From Fedora Project Wiki
(Yum vars aren't allowed for pykickstart) |
(Fix macro) |
||
| Line 14: | Line 14: | ||
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 <code>#</code>). The updates-testing repo command should always be commented out. | 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 <code>#</code>). The updates-testing repo command should always be commented out. | ||
* <code><nowiki>repo --name=rawhide --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=i386</nowiki></code> | * <code><nowiki>repo --name=rawhide --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=i386</nowiki></code> | ||
* <code | * <code>repo --name=fedora --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-{{FedoraVersionNumber|next}}&arch=i386</code> | ||
* <code><nowiki>repo --name=updates --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f$releasever&arch=i386</nowiki></code> | * <code><nowiki>repo --name=updates --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f$releasever&arch=i386</nowiki></code> | ||
* <code><nowiki>#repo --name=updates-testing --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-testing-f$releasever&arch=i386</nowiki></code> | * <code><nowiki>#repo --name=updates-testing --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-testing-f$releasever&arch=i386</nowiki></code> | ||
Revision as of 02:53, 13 October 2010
Spins repo directives
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 because it is used with pungi, not livecd-creator. Otherwise it would pull all packages that satisfy dependencies rather than just one.
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=i386repo --name=fedora --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-41&arch=i386repo --name=updates --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f$releasever&arch=i386#repo --name=updates-testing --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-testing-f$releasever&arch=i386
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.