[mirror-admin] rsync and updates-testing -> updates-released

[Axel Thimm]

On Tue, Jul 21, 2009 at 08:38:23PM -0700, Jesse Keating wrote:
> On Tue, 2009-07-21 at 23:03 -0300, Carlos Carvalho wrote:
> > Right now they cannot be absolute for the same reason. I meant
> > "absolute" starting from the root of the mirror tree, of course.
> > 
> 
> I got push back even on that.  Doing it in repodata is a tad bit
> dangerous, so I'd rather do it with file hardlinks.
> 
> Why is there an aversion to hardlinks?

hardlinks are good, the directory should be dot-hidden, so users don't
get confused and should probably live under updates/testing/, best
perhaps under updates/testing/<release>/<arch>/.allupdates

The alternative place would be under updates/<release>, but some
mirrors may be filtering out updates/testing, and they would then
still get all updates through a backdoor. .allupdates under
updates/testing/<release>/<arch> makes sense, as any mirror mirroring
an updates/testing tree would be mirroring the analog updates-releases
tree as well (hopefully onto the same filesystem ...).

Whichever mirror doesn't like this approach can still --exclude
.allupdates/ and would have the same behaviour as today (although that
would not be recommended due to double-downloading updates).
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://mail.ale.org/pipermail/mirror-admin/attachments/20090722/39c23a25/attachment.bin 
-------------- next part --------------
--