Kris,
What about people who build the install packages (i.e. rpms, debs, etc).
What process do they follow? Do they build from source? Do they use
prebuilt files provided on the website? What files would we expect they
include? When jdbc was part of the base distribution these were easy
questions; all you installed in the rpms was the jar file since the doc
was all handled separately in it's own rpm. Now we need to figure this
out ourselves.
For consistency I think we need to have some packaging instructions that
provide guidance on what an install of the jdbc driver should contain
(clearly it needs one or more of the jar files, should also include the
doc - in what formats though, html, pdf, etc, and probably also should
include the example source code).
If many (most?) users of the jdbc driver get it through prebuilt
packages, then we need to spend some time thinking about these issues,
so that these users have a reasonable environment to work in.
thanks,
--Barry
Kris Jurka wrote:
>
> I've reconsidered my scheme to package docbook stylesheets, dtds, and
> saxon in a separate jdbc documentation package. After realizing that the
> number of people who will ever build the documentation can comfortably be
> counted on my digits, a little complexity isn't going to kill us. I've
> added Oliver's validation target to the build file and added the ability
> to specify the dtd and stylesheet locations via a local properties file
> (build.local.properties). This will allow overriding any default config
> parameter for a local setup. My build.local.properties for a debian
> system looks like:
>
> docbook.stylesheet=/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/xhtml/chunk.xsl
> docbook.dtd=/usr/share/sgml/docbook/dtd/xml/4.2
>
> Kris Jurka
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
