Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> ... the file
>> that is actually being delivered in snapshots still contains man1/
>> and manl/. So that file needs to be regenerated. Peter?
> Shouldn't it be part of the nightly snapshot creation to make that file?
> In the snapshot I just downloaded its date is yesterday.
The tar file's own date might be yesterday, but its contents are dated
2003-11-02 ... and indeed look to be that old. So something's bollixed
in the snapshot generation process.
Historically the man.tar.gz files were created manually because there
were some manual fixups needed to the generated man files. I'm not sure
what vestiges of that still remain --- Peter's generally been the one to
take care of it. But we definitely aren't shipping a freshly generated
copy in the nightly snapshot right now.
If we do have a fully automated process now, it's probably fair to ask
why there's an internal tarball involved at all, rather than just
shipping the built man1/ and man7/ subdirectories (and likewise for the
html). Double compression of that data isn't going to be helpful.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
