General suggested naming scheme

The currently preferred naming scheme allows :

• Multiple distribution trees
• Multiple versions organized by distribution
• Multiple languages of the same distribution version
• Multiple architectures organized by distribution version
• Multiple branches (main distribution, the updates, extras...) for single line source.list entries

It is as follows :

rpm http://host.domain.ext/dir/subdir distr/ver/lang/arch mod1 mod2 ... modn

Suggestions :

• Having a dedicated virtualhost is recommended since you will then avoid needing the "dir/subdir" part in the URL (resulting in a shorter sources.list entry)
• If you cannot have a dedicated virtualhost, using "/apt" or "/apt-rpm" as the trailing part of the URL is considered the cleanest and easiest solution
• A trailing extra unuseful name is spared with the "--flat" option when creating the repository (default since 0.5.x?) since this allows to have RPMS.* and SRPMS.* in the same place, thus not mixing SRPMS between architectures (a good thing, as often a few source packages are architecture specific, unfortunately).
• The basic module names should be "os" for the main distribution and "updates" for its updates, as those names are quite clear and not redundant with any part of the URL

Examples :

rpm http://apt.rpm.foo redhat/8.0/en/i386 os updates freshrpms
rpm http://apt.rpm.foo redhat/6.2/en/i386 os powertools updates

Examples of complex naming to avoid :

rpm http://apt.rpm.foo/mirror/redhat/apt redhat-8.0-os/redhat-i386 os
rpm http://apt.rpm.foo redhat-8.0/i386 redhat
rpm http://apt.rpm.foo redhat-8.0-updates/i386 redhat