Hosting and repo layout

[Matthias Saou]

Thorsten Leemhuis wrote :

> This is what it would look like when we want to replicate the Fedora
> layout (example only for el5 and Fedora 8/development; both only i386 to
> keep things simple):
> .
> `-- free
>     |-- el
>     |   |-- 5
>     |   |   `-- i386
>     |   |       |-- all_the.rpms
>     |   |       `-- repodata
>     |   `-- testing
>     |       `-- 5
>     |           `-- i386
>     |               |-- all_the.rpms
>     |               `-- repodata
>     `-- fedora
>         |-- development
>         |   `-- i386
>         |       `-- os
>         |           `-- repodata
>         |-- releases
>         |   `-- 8
>         |       |-- AddOn
>         |       |   `-- addon.i386.iso
>         |       |-- Everything
>         |       |   `-- i386
>         |       |       `-- os
>         |       |           |-- all_the.rpms
>         |       |           `-- repodata
>         |       |-- Live
>         |       |   `-- coolspin.i386.iso
>         |       `-- RPMFusion
>         |           `-- i386
>         |               |-- iso
>         |               |   `-- rpmfusion_spin.iso
>         |               `-- os
>         |                   |-- repodata
>         |                   `-- subset_of_everything.rpms
>         `-- updates
>             |-- 8
>             |   `-- i386
>             |       |-- all_the.rpms
>             |       `-- repodata
>             `-- testing
>                 `-- 8
>                     `-- i386
>                         |-- all_the.rpms
>                         `-- repodata
> Benefits:
>  - people are used to the layout
>  - room for spins, add-on CDs
> Disadvantage:
>  - might be more complicated than actually needed
> 
> Comments?

Why "free" (and I suppose another similar tree for nonfree) at the
root? I'd prefer to not separate free/nonfree completely, just users
enable or disable either easily, and mirror admins be able to exclude
"nonfree" and be done with it. Making them be two completely separate
trees/websites/etc will only make things overly complex for nothing.

The other thing we need to be sure about before deciding on the tree is
if we want to have a frozen "release" set of packages, known to be
compatible with the original CD/DVD images plus updates, or if we want
to be a moving target, only compatible with release+updates, possibly
making our repositories incompatible with the original CD/DVD images at
some point, unless users also enable updates at install time.

I'd prefer going with a frozen "release" set of packages, from which we
can also later make a CD or DVD image, to make it possible to install
RPM Fusion packages on computers which aren't connected to the network.

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 7 (Moonshine) - Linux kernel 2.6.22.6-81.fc7
Load : 0.28 0.29 0.27