|
|
| (4 intermediate revisions by the same user not shown) |
| Line 3: |
Line 3: |
| == Where are they == | | == Where are they == |
|
| |
|
| There are repo directives in the kickstart file for a few base spins. Currently: | | There are repo directives in the following files: |
| * fedora-live-base | | * fedora-repo.ks |
| * fedora-aos | | ** This is included by spins (often indirectly). |
| * fedora-live-mini | |
| * fedora-install-fedora | | * 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. | | ** This one uses different repos than normal spins and can't include fedora-repo.ks. |
| | | There are instructions in the two files on what should and shouldn't be commented out depending on whether or not it is the master branch of spin-kickstarts. |
| == 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 <code>#</code>). The updates-testing repo command should always be commented out.
| |
| * <code>repo --name=rawhide --mirrorlist=<nowiki>http://mirrors.fedoraproject.org/mirrorlist?</nowiki>repo=rawhide&arch=$basearch</code>
| |
| * <code>repo --name=fedora --mirrorlist=<nowiki>http://mirrors.fedoraproject.org/mirrorlist?</nowiki>repo=fedora-$releasever&arch=$basearch</code>
| |
| * <code>repo --name=updates --mirrorlist=<nowiki>http://mirrors.fedoraproject.org/mirrorlist?</nowiki>repo=updates-released-f$releasever&arch=$basearch</code>
| |
| * <code>#repo --name=updates-testing --mirrorlist=<nowiki>http://mirrors.fedoraproject.org/mirrorlist?</nowiki>repo=updates-testing-f$releasever&arch=$basearch</code>
| |
|
| |
|
| == When to change which repo(s) is used == | | == 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. | | The repo commands should be changed when the master branch is branched. |
| | |
| * When development is branched, the rawhide repo command should be commented out and the fedora repo command should be uncommented in the master branch. (If an empty updates repo is created already then the updates repo should also be uncommented so we don't have to do a release to change it just before release.)
| |
| * When the git repo is branched shortly before a release the rawhide repo command should be uncommented and the fedora repo command should be commented out in the master branch. The updates repo command should be uncommented in the new branch corresponding to the pending release.
| |
Spins repo directives
Where are they
There are repo directives in the following files:
- fedora-repo.ks
- This is included by spins (often indirectly).
- fedora-install-fedora
- This one uses different repos than normal spins and can't include fedora-repo.ks.
There are instructions in the two files on what should and shouldn't be commented out depending on whether or not it is the master branch of spin-kickstarts.
When to change which repo(s) is used
The repo commands should be changed when the master branch is branched.
