Bug#61991: potato/frozen directories refer to slink directories
On Fri, Apr 07, 2000 at 09:59:30PM -0400, Daniel Barclay wrote:
> > > Some files in the potato/frozen hierarchy are links into the slink
> > > hierarchy. This means one cannot mirror just the potato/frozen
> > > version without mirroring slink.
> > Of course, this is expected. It is done to save space on full mirrors.
> > When potato releases, slink moves out, and then symlinks will be replaced
> > with real files.
> Does it save much space anymore? (Most packages in potato are
> new by now, right?)
Most, but not all. In another message to this thread counted about 180 that
> Are mirroring tools flexible enough to keep symbolic links like
> those from binary-i386 to binary-all within a release (e.g., potato)
> while copying files linked across release?
> If not, it seems that the linking across release makes it a lot harder
> to mirror potato to try it out (one has to mirror slink also,
> taking up a lot more space).
I would expect an advanced mirroring tool to be able to get one type of
symlinks, and dereference another; however I don't know if it's possible.
The problem with `flattening' symlinks to files in potato now is that
it would make the mirror pulse much much larger, since they'd have to
remirror all those files (pointless since they already have them :/),
so those things are delayed until the release, when one would expect
an impact in bandwidth.
Digital Electronic Being Intended for Assassination and Nullification