Legacy mirror structure

[Dennis Gilmore]

Once upon a time Monday 19 January 2004 9:11 pm, Matthias Saou wrote:
> Jesse Keating wrote :
> > My proposal is to run a master mirror server for FL.  An ISP has offered
> > rackspace and bandwidth for such a beast.  The layout I envision is this:
<snip>
> Are these SRPMS symlinks really useful? Why not this instead :
> $releasever/{base,updates,..}/{$basearch,SRPMS}/*.rpm
> Just a thought.
>
> [...]
>
> > Thoughts?
>
> Yes, one more important one : As it is planned to support at least some
> Fedora Core releases later on, the information about "redhat" vs. "fedora"
> should appear somewhere, otherwise there will clearly be a scalability
> problem once Fedora Core 9 needs to be supported ;-) I'd suggest :
>
> /legacy/{redhat,fedora}/$releasever/...
perhaps go with numbers for Red Hat but use a leading FC for fedoracore
/pub/fedoralegacy/FC1/
/pub/fedoralegacy/7.3/

> Also, for the ftp/rsync accessible structure, having the leading /legacy/
> part of the path is a good thing (as /pub/legacy for ftp and as a "legacy"
> rsync module for instance), but for http it's quite redundant with the
> virtual host name, and could be removed for purely cosmetic and line length
> considerations.

I really think that just using legacy will make it hard to distingush what its 
for on mirrors  what if some mandrake legacy project starts up users may be 
confused.  

Dennis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
URL: <http://listman.redhat.com/archives/fedora-legacy-list/attachments/20040119/d7fa9948/attachment.sig>