From Fedora Project Wiki
m (typo) |
(Note the timing) |
||
| Line 7: | Line 7: | ||
* fedora-aos | * fedora-aos | ||
* fedora-live-mini | * fedora-live-mini | ||
* fedora-install-fedora (This one | * fedora-install-fedora (This one shouldn't be changed as it is set up a bit differently.) | ||
== What should they contain == | == What should they contain == | ||
| Line 16: | Line 16: | ||
* <code><nowiki>repo --name=fedora-updates --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f$releasever&arch=$basearch</nowiki></code> | * <code><nowiki>repo --name=fedora-updates --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f$releasever&arch=$basearch</nowiki></code> | ||
* <code><nowiki>#repo --name=fedora-updates-testing --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-testing-f$releasever&arch=$basearch</nowiki></code> | * <code><nowiki>#repo --name=fedora-updates-testing --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-testing-f$releasever&arch=$basearch</nowiki></code> | ||
== When to change which repo(s) is used == | |||
The idea is to have the repos point to repo that will next be used to build spins. | |||
* When development is branched, the rawhide repo command should be commented out and the fedora and fedora-updates repo commands should be uncommented. | |||
* When the git repo is branched shortly after a release the rawhide repo command should be uncommented and the fedora and fedora-updates repo commands should be commented out. | |||
Revision as of 10:04, 30 August 2010
Spins repo directives (draft)
Where are they
There are repo directives in the kickstart file for a few base spins. Currently:
- fedora-live-base
- fedora-aos
- fedora-live-mini
- fedora-install-fedora (This one shouldn't be changed as it is set up a bit differently.)
What should they contain
They should contain the following repo commands with either the rawhide repo command or both of the fedora and updates repo commands commented out (using a leading #). The updates-testing repo command should always be commented out.
repo --name=rawhide --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=$basearchrepo --name=fedora --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearchrepo --name=fedora-updates --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f$releasever&arch=$basearch#repo --name=fedora-updates-testing --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-testing-f$releasever&arch=$basearch
When to change which repo(s) is used
The idea is to have the repos point to repo that will next be used to build spins.
- When development is branched, the rawhide repo command should be commented out and the fedora and fedora-updates repo commands should be uncommented.
- When the git repo is branched shortly after a release the rawhide repo command should be uncommented and the fedora and fedora-updates repo commands should be commented out.