[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Multiple yum transactions in kickstart

My experience has been that the system is not really installed until anaconda has completed its post installpackages steps. This may also include some user specified %post scripts.

I've used kickstart %post scripts to configure additional repos and install additional RPMS.
The caveats being:
- network configuration is required - it would be nice to have a way to specify addditional ISO repos via kickstart
 - inter-repo package dependencies should be worked out ahead of time


On Aug 19, 2010, at 12:02 AM, Jon Stanley wrote:

It would be an *extremely* useful feature of Anaconda to be able to
have multiple yum/rpm transactions in the context of a single
kickstart. I would propose that this be accomplished by having a new
transaction every time you encounter %packages. I know that this
sounds like an oddball request, but let me explain the reasoning.

There are (very often) RPMs that you wish to install at kickstart time
that are not RH/Fedora content that you have no control over. These
third parties may or may not know how to package things and make them
dependency complete for installation at kickstart-time (and assume
that you're going to install them on an already-installed system, for
example), or do completely crazy things, like have %pretrans scripts,
which aren't very useful in the install environment.

I'm not all that familiar with anaconda internals, but this doesn't
sound like major surgery to me - just take the existing code, and wrap
it into something that can be executed multiple times. This behavior
is obviously completely optional, if you only have one %packages
section in your kickstart, it behaves the same way it does today.

Let me know if further detail on the use case is required.

Anaconda-devel-list mailing list
Anaconda-devel-list redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]