Personal tools
You are here: Home Documentation Revisor Configuration Files

Revisor Configuration Files

A short intro to the Revisor Configuration Files

Revisor Configuration Files

First of all, this is what configuration files come with your installation of Revisor:

[kanarip@elwood ~]$ rpm -qlcp revisor
/etc/pam.d/revisor
/etc/revisor/conf.d/revisor-f7-i386.conf
/etc/revisor/conf.d/revisor-f7-ppc.conf
/etc/revisor/conf.d/revisor-f7-x86_64.conf
/etc/revisor/conf.d/revisor-fc6-i386.conf
/etc/revisor/conf.d/revisor-fc6-ppc.conf
/etc/revisor/conf.d/revisor-fc6-x86_64.conf
/etc/revisor/conf.d/revisor-rawhide-i386.conf
/etc/revisor/conf.d/revisor-rawhide-ppc.conf
/etc/revisor/conf.d/revisor-rawhide-x86_64.conf
/etc/revisor/conf.d/sample-full.cfg
/etc/revisor/conf.d/sample-ks.cfg
/etc/revisor/conf.d/sample-live-games.cfg
/etc/revisor/comps-f7.xml
/etc/revisor/comps-fc6.xml
/etc/revisor/revisor.conf
/etc/security/console.apps/revisor

Of course the /etc/pam.d/revisor and /etc/security/console.apps/revisor files do not need any editing at all. The other files in /etc though are quite important. We'll start with /etc/revisor/revisor.conf

/etc/revisor/revisor.conf

The master Revisor configuration file can help you with many, many settings. In fact, all of them. The first section, "revisor" hold configuration items that can influence the flow of the program. One example is:

# Types of Installation Media to build
media_installation_dvd=1
media_installation_cd=0

# Types of Live Media to build
media_live_optical=1
media_live_thumb=0

which lets you configure which types of media exactly should be composed. In the GUI you'll have plenty of opportunity to change it, but the CLI requires you to set either these configuration parameters, or specify them as parameters from the command-line.

Here's another few examples:

# Should we, generally speaking, enable development repositories?
repos_enabledevelopment=1

# Or testing repositories?
repos_enabletesting=0

# How about source repositories?
repos_enablesource=0

# And debuginfo repositories?
repos_enabledebuginfo=0

For a complete reference of configuration options, check out our page on 'Revisor Configuration - All the options'

Then, revisor.conf lets you list what we call 'models'. An example is:

[f7-i386]
main = /etc/revisor/conf.d/revisor-f7-i386.conf
product_name = Fedora
product_path = Fedora
iso_basename = F
comps = /etc/revisor/comps-f7.xml
architecture = i386
version = 7
getsource = 0
release_pkgs = ^fedora-release.*$ ^fedora-release-notes.*$
release_files = eula.txt fedora.css GPL README-BURNING-ISOS-en_US.txt RELEASE-NOTES-en_US.html ^RPM-GPG images img stylesheet-images
copy_dir = /path/to/some/directory
strip_copy_dir = /path/to/some

Of course you can list as many models as you want, and specify some of the specific settings here. Again, such a model lets you redefine some of the options. Rawhide models for example will need to have repos_enabledevelopment set to 1, while the global configuration doesn't.

Setting values description
main File with yum configuration
This is a mandatory configuration directive. It should point to a valid yum configuration file, with all variables expanded (ergo: $basearch and $releasever variables)
product_name String The Product Name for this model.
product_path
String
The path on the image in which the RPMs end up.
iso_basename
String
The base name for the resulting ISO. Revisor will add version and architecture, including media type and, if appropriate, disc number
comps
File
This should be a readable and valid comps file. It is used when the ISO Image's repository is created, and is thus mandatory.
architecture
Architecture
Architecture this model is for. Any compatible architecture on the host machine is acceptable. Remember the yum configuration should match with what you set here.
version
String
A version 'number'. It doesn't necessarily need to be a number, though
getsource
0, or 1
Whether to get the source and create that media as well, so you can officially distribute your own compose.
release_pkgs
Regexp
Regular Expression that indicates the packages Revisor extracts so you can copy data from them. This is especially usefull for rebranding, since for a Fedora spin, these packages are the fedora-release and fedora-release-notes packages. If you add a 3rd party or private repository, you can also add the appropriate release RPM from that repository to this Regexp and have the RPM keys available.
release_files
Regexp
Regular Expression that indicates what files from 'release_pkgs' should become available on the installation media. You may want to keep a model which has the defaults, and then work your way from there.
copy_dir
Directory
From your current system, copy a directory tree over to the installation media. This is useful in cases where you want kickstart %post scripts to be able to copy, for example, a prepped httpd.conf. The entire copy_dir directory will end up on in the files/ directory on your media. With the next configuration setting, you can ultimately tweak that, considering system administrators will have a directory like /data/images/settings//etc/httpd, but do not want files/data/images/settings/etc/httpd/ on their media, rather then just files/etc/httpd
strip_copy_dir
String
Using strip_copy_dir, we adjust copy_dir and strip off whatever you specify here. Files will still end up in the tree below files/ nontheless.

The Way Revisor Handles Configuration

Revisor has been developed to run in either a GUI, or CLI mode, but that doesn't mean they are mutually exclusive. When running Revisor, all configuration possibilities are taken into consideration:

  1. Configuration defaults are set from hard coded statements
  2. Some of the command line parameters are taken into consideration, such as the --config, and --model parameters. The configuration file is read and options specified in the configuration file are set.
  3. Options from the command line other then the --config or --model are being parsed and set whatever other configuration items you have specified.
  4. If you are running in GUI mode, you'll be able to adjust the configuration from the dialogs presented.
Note that some configuration options have CLI equivalents, and other do not. Feel free to submit a patch, but from our perspective, adding all configuration items as CLI parameters is just as easy as digging in the configuration file.
Document Actions
Log in


Forgot your password?