Folks,
This is the most recent directory structure proposal from our friends at
Red Hat. Of course they will not include Legacy, but they have given us
a pretty detailed directory structure to follow.
Jack Neely
----- Forwarded message from Bill Nottingham <notting@xxxxxxxxxx> -----
From: Bill Nottingham <notting@xxxxxxxxxx>
To: mirror-list-d@xxxxxxxxxx
Subject: updated Fedora mirror layout proposal
Date: Wed, 29 Oct 2003 09:54:21 -0500
Updated proposal; I hope I've addressed the various
concerns.
Things marked with { } are not on the Red Hat hosted
server, but more or less marked here as to where they
might fit in if someone wanted to mirror other people's
work there.
Things marked with "*" indicate a probable yum repository.
... = repeat as necessary. If it's not clear how to complete
this, please respond. :)
Everything is under /pub/fedora/linux in the following scenario:
core/
core/
core/1
core/1/SRPMS
core/1/%arch
core/1/%arch/iso/
core/1/%arch/debug/ *
core/1/%arch/os *
core/1/%arch/os/SRPMS -> ../../SRPMS
core/1/%arch/os/Fedora
core/1/%arch/os/images ...
core/2/ ...
core/updates
core/updates/1
core/updates/1/SRPMS
core/updates/1/%arch/ *
core/updates/1/%arch/SRPMS -> ../SRPMS
core/updates/1/%arch/debug *
core/updates/2 ...
core/updates/testing/1
core/updates/testing/1/SRPMS
core/updates/testing/1/%arch/ * ...
core/development
<insert current rawhide tree here>
core/test
core/test/1.9
<repeate core/1/ structure>
core/test/1.95 ...
extras/1/
extras/1/SRPMS
extras/1/%arch *
extras/1/%arch/SRPMS -> ../SRPMS
extras/1/%arch/debug *
extras/1/testing
extras/1/testing/SRPMS
extras/1/testing/%arch *
extras/1/testing/%arch/SRPMS -> ../SRPMS
extras/1/testing/%arch/debug
extras/2 ...
alternatives/1/
<repeat extras structure>
{ legacy / }
<repeat extras structure>
Changes here:
- easy to exclude extras, or alternatives, or legacy, or rawhide, or
particular versions of releases
- once downloaded, core/<version> shouldn't have to change
Given a download server of download.fedora.redhat.com, basically, you'd
have something like this as a yum setup (convert to up2date, or whatever):
[base]
name=Fedora Core $releasever - $basearch
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/$releasever/$basearch/os/
[base-debug]
name=Fedora Core $releasever - $basearch - debug information
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/$releasever/$basearch/debug/
[updates]
name=Fedora Core $releasever - Updates
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/$releasever/$basearch/
[updates-debug]
name=Fedora Core $releasever - Updates
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/$releasever/$basearch/debug/
[updates-testing]
name=Fedora Core $releasever - Updates
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/$releasever/testing/$basearch/
[updates-testing-debug]
name=Fedora Core $releasever - Updates
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/$releasever/testing/$basearch/debug/
[rawhide]
name=Fedora Core Development Stream
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/development/
In a default installation, [base] and [updates] would be active, the rest would be
commented out.
Does this make sense/look sane?
--
----- End forwarded message -----
--
Jack Neely <slack@xxxxxxxxxxxxxxx>
Realm Linux Administration and Development
PAMS Computer Operations at NC State University
GPG Fingerprint: 1917 5AC1 E828 9337 7AA4 EA6B 213B 765F 3B6A 5B89
