Bob Huisman wrote:
I am currently writing a kickstart script that must install a base system and some custom packages. Each of those packages has 2 'versions', a fully automated one and one that just deploys the software. Which version to deploy is determined by an environment variable read in the .spec file. I have been thinking about making a package which sets some of the environment variables, and have that installed too, but I understood that the order of installation of packages is not always the same... As the system has just been installed, there are no pre-set environment variables which can be used. I was wondering whether and how it is possible to set an environment variable before installation of any custom packages? I am using RHEL 5 with RHN Satellite 5 beta. Anyone who has a suggestion on how to deal with this problem? Thanks in advance!
One can set environment variables from the commandline when booting the kernel. Any "key=val" pairs appear in the environment.
-- Cheers John -- spambait 1aaaaaaa@xxxxxxxxxxxxxxxx Z1aaaaaaa@xxxxxxxxxxxxxxxx Please do not reply off-list
