Re: Legacy mirror structure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

Attachment: pgp00198.pgp
Description: signature


[Index of Archives]     [Fedora Development]     [Fedora Announce]     [Fedora Legacy Announce]     [Fedora Config]     [PAM]     [Fedora General Discussion]     [Big List of Linux Books]     [Gimp]     [Yosemite Questions]

  Powered by Linux