[Revisor-users] Some questions on comps.xml and kcikstart file

[Jeroen van Meeuwen]

Alexander Todorov wrote:
> Hello,
> I've read the archives and as it seems comps.xml is edited manually.
> Does Revisor include functionality to merge comps.xml from multiple 
> repositories used to build the tree?
> 

Yes, Revisor (by default) will use all the comps.xml files it gets from 
the repositories configured, and merges those into a comps file that is 
to be used during the installation.

> As I understand there is no automatic comps.xml generator for now.
> Anybody has info if there is some work in progress ?
> 
> Regarding the kickstart file:
> I couldn't find what options will Revisor read from the kickstart file 
> used when building a tree. Sure a %packages or additional repos make 
> sense for building the tree. However other options don't. E.g. network 
> configuration in the case where we build only installable trees and not 
> livecd and the ks.cfg is not used for automatic installation from that CD.
> Is there some documentation that outlines what kickstart options are 
> used in various Revisor use cases (livecd, install media, ks.cfg on disc)?
> 

Revisor just takes a kickstart file and parses all the options available 
in kickstart. Depending on what it is Revisor needs to do with the 
kickstart file however, some options will be used while others won't.

Usually when creating installation media, only the %packages section is 
being used, though if you specify one of these options:

--kickstart-save=/path	# Saves the kickstart file to a file /path
--kickstart-include	# Includes the kickstart file in the tree
   --kickstart-default	# Sets the included kickstart file to be the
			  default option in the bootloader menu

Revisor takes these actions and all the configuration in the kickstart 
file that doesn't necessarily looks useful for the actual compose of the 
installation media, becomes useful when /using/ the installation media 
-each in their own way.

Kind regards,

Jeroen van Meeuwen
-kanarip