Re: 7.2.7 -> 8.0.1 Bundles Ready ... - Mailing list pgsql-hackers

From Dave Page
Subject Re: 7.2.7 -> 8.0.1 Bundles Ready ...
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E45287E0@ratbert.vale-housing.co.uk
Whole thread Raw
In response to 7.2.7 -> 8.0.1 Bundles Ready ...  ("Marc G. Fournier" <scrappy@postgresql.org>)
Responses Re: 7.2.7 -> 8.0.1 Bundles Ready ...  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers

> -----Original Message-----
> From: Marc G. Fournier [mailto:scrappy@postgresql.org]
> Sent: 31 January 2005 22:35
> To: Tom Lane
> Cc: Dave Page; pgsql-hackers@postgresql.org; David Fetter
> Subject: Re: [HACKERS] 7.2.7 -> 8.0.1 Bundles Ready ...
>
> On Mon, 31 Jan 2005, Tom Lane wrote:
>
> > "Dave Page" <dpage@vale-housing.co.uk> writes:
> >> /pub/src/v8.0.1 is missing :-(
> >
> > Why do we even have individual symlinks in pub/src?  Seems to me we
> > could replace the whole src directory with a symlink to source, and
> > eliminate one bit of release bookkeeping ...
>
> the symlinks wre to make Peter happy ... he didn't like the
> 'v' in the
> directory name, so we make the src directory that has
> 'non-v'd symlinks :)
>
> And yes, that is the *only* reason there is a src directory ...

Urgh. No offence to Peter, but I think it's a helluva lot messier having
all those symlinks. Not to mention the binary/ dir which doesn't have a
non-v'ified bin/X.X.X equivalent. Can we lose /src and just keep /source
and /binary (personally I don't care whether or not we keep the v's on
the subdirs)?

It probably causes a lot of bandwidth to be wasted as well - I recently
found a mirror site that was mirroring the entire ftp ste using about 20
simultaneous ftp connections. I'll bet that didn't copy the symlinks as
symlinks and instead grabbed all the files again, each time it tried to
'sync'. I barred that particular site in the ftpd conf, but there could
be others of course.

Regards, Dave


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: New 7.2.7 Bundle Up
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] Bug in create operator and/or initdb