Rahul Sundaram wrote:
Pungi behaviour seems pretty different from livecd-creator, I am used
to. A few things
* Adding a package to the kickstart file doesn't seem to make it
installed by default. Other than changing comps, what's the best way to
add some apps as default?
The kickstart package manifest defines what is the RPM payload on the media.
* Some packages are there to enable a default install with the best
packages. Comps helps there, of course.
* Some packages are there as commonly used alternatives. They may be
selected during manual package selection, during upgrades, or
* Some packages are on the media to provide an upgrade path.
* Some packages are pulled in to meet a dependency although a "yum
install" for a package requiring a capability would not drag in that
package to meet the requirement. This is due to inclusive dependency
resolving, but also (partly) goes to upgrade paths.
* Doing the following doesn't help in rebranding
Using inclusive dependency resolving, fedora-release and fedora-logos
packages should end up on the media, as every package providing
"system-release" or "system-logos" is pulled in when a requirement for
either of these is encountered.
How does one go about excluding a few packages and having others
available by default?
You either --exclude the packages in the "repo" configuration directive
used in the kickstart, so you would be using packageSack excludes
(similar to the exclude= parameter in YUM), but that isn't passed on to
anaconda's buildinstall. buildinstall as such will look for
'system-release' and find 'fedora-release' -same goes for fedora-logos.
* Why does the -devel files get installed?
Some packages require what -devel has to offer, and some -devel packages
are in comps groups.
Jeroen van Meeuwen