From Fedora Project Wiki

(Note the timing)
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Spins repo directives (draft) =
= Spins repo directives =


== 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.)
** 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><nowiki>repo --name=rawhide --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=$basearch</nowiki></code>
* <code><nowiki>repo --name=fedora --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$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>


== 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 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.

Latest revision as of 16:44, 29 June 2013

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.