On tis, 2009-08-11 at 12:42 +0300, Peter Eisentraut wrote:
> I've been thinking that we could actually get rid of that build-in-srcdir
> behavior, which also occasionally puzzles vpath users with respect to gram.c
> and so on. The new behavior would be to build targets in the local
> directory.
On Tuesday 11 August 2009 17:02:01 Tom Lane wrote:
> Having all the derived files in the build directory definitely seems
> to me to reduce the complexity and surprise factor, so +1 for changing.
I've looked at that briefly, and it's a bit more complicated than it would
appear. I will figure thi
Peter Eisentraut writes:
> I've been thinking that we could actually get rid of that build-in-srcdir
> behavior, which also occasionally puzzles vpath users with respect to gram.c
> and so on. The new behavior would be to build targets in the local
> directory.
> The only requirement would b
On Monday 10 August 2009 21:53:57 Alvaro Herrera wrote:
> I understand that the placement of the generated docs in the sourcedir
> instead of the builddir is so that it is included in the tarball,
> correct? I admit I was surprised by that change.
I did point that out upthread, with you in partic
Peter Eisentraut wrote:
> On Monday 10 August 2009 18:43:26 Bruce Momjian wrote:
> > Are you sure you don't want the results in doc/src/man1 and
> > doc/src/html? Or even doc/man1 and doc/html?
>
> I am in fact not sure, but people are used to working on doc/src/sgml, so
> keeping the main action
On Monday 10 August 2009 18:43:26 Bruce Momjian wrote:
> Are you sure you don't want the results in doc/src/man1 and
> doc/src/html? Or even doc/man1 and doc/html?
I am in fact not sure, but people are used to working on doc/src/sgml, so
keeping the main action there seemed reasonable. If we eve
Peter Eisentraut wrote:
> So the next step to documentation bliss is to get rid of the man.tar.gz and
> postgres.tar.gz tarballs that are shipped inside the tarball. These are
> historical artifacts from the era when building the documentation for release
> required manual interference, and tha
On Wednesday 05 August 2009 16:13:48 Magnus Hagander wrote:
> Just to verify, there is not going to be any changes in the actual
> format of the generated files, right?
Correct.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www
On Wed, Aug 5, 2009 at 09:24, Peter Eisentraut wrote:
> So the next step to documentation bliss is to get rid of the man.tar.gz and
> postgres.tar.gz tarballs that are shipped inside the tarball. These are
> historical artifacts from the era when building the documentation for release
> required m
So the next step to documentation bliss is to get rid of the man.tar.gz and
postgres.tar.gz tarballs that are shipped inside the tarball. These are
historical artifacts from the era when building the documentation for release
required manual interference, and that era ended yesterday at the lat
10 matches
Mail list logo
