Spins repo directives

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Fix "updates" name)
(Updates repos seem to be created at branch these days)
Line 22: Line 22:
 
The idea is to have the repos point to repo that will next be used to build spins.
 
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 repo command should be uncommented in the master branch.
+
* 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.
 
* 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.

Revision as of 14:03, 12 February 2012

Contents

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=$basearch
  • repo --name=fedora --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch
  • repo --name=updates --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f$releasever&arch=$basearch
  • #repo --name=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 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.