I'm contemplating our RPM installation process, and have the following
thoughts:
- we currently use installer.pl, which has worked pretty well.
- we are about to add additional optional packages to the install
process, and now have quite a few optional packages for a server
install:
o flamethrower
o systemimager-flamethrower
o systemimager-boot<arch1>-standard
o systemimager-boot<arch2>-standard
o systemimager-boot<arch1>-<flavor2>
o systeminstaller
o systemimager-client or systemimager-server or both
- is there some way to use the rpm version of "apt-get" for all rpm
distros? and if so, should we consider using it?
- should we modify the options used with installer.pl?
Currently we have the following options:
installer [--help] [--verbose] [--tag {CSM|devel|stable}]
[--bootarch {none|all|i386|ia64|ppc64|ppc64-iSeries}]
< --download | --install {client|server|both} >
--help
--verbose
--tag TAG Download the tag packages. Defaults to stable.
TAG can be one of "CSM", "devel", "stable".
(requires --download)
--file Use local file instead of downloading a tag file.
--download Download the packages.list file, and all packages
to the download directory. (overwrites existing
packages.list file)
--location Use alternative download directory (defaults to
'/tmp/sis-packages')
--install TYPE Install packages for this type of system. TYPE can
be "client", "server", or "both".
--bootarch TYPE Download the boot rpm(s) for the specified arch.
'all' downloads all available. Defaults to
architecture of the host machine.
One way we could try to deal with these options in a flexible
and easy to understand way is:
- remove the bootarch option
- add a --list option, that shows a listing of the basename of all
available packages.
- add a --package option to take a series of package names
- change the --install option to be boolean (only means "yes" install
the packages)
- assume --download, if --install, unless package already exists in
the local download directory.
A listing might then look like this:
installer --list
flamethrower
perl-AppConfig
perl-MLDBM
systemconfigurator
systemimager-i386boot-standard
systemimager-ia64boot-standard
systemimager-ppc64-iSeriesboot-standard
systemimager-ppc64boot-standard
systemimager-common
systemimager-flamethrower
systemimager-server
systemimager-client
systeminstaller
systeminstaller-x11
installer --install --package systeminstaller
(and the script would download systeminstaller, then query it for
dependencies. if any of it's dependencies are available in the tag
file, then it downloads them and proceeds in the same way. if the
dependencies are not available in the tags file, then it would be up
to the user to satisfy them)
or an install could look like:
installer --install --package systemimager-client
or
installer --install --package systemimager-server \
systemimager-ppc64boot-standard \
systemimager-ia64boot-standard \
systemimager-flamethrower
or
installer --install --package systemconfigurator
or
installer --install --package flamethrower
You get the idea.
-Brian
--
---------------------------------------------------------
Brian Elliott Finley Argonne, MCS Division
Phone: 630.631.6621 http://thefinleys.com
GPG: 3FF8 D096 0E0C D3F3 29B7 6518 D20B 1931 10F8 EE52
---------------------------------------------------------
-------------------------------------------------------
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
http://www.wrgsurveys.com/2003/osdntech03.php?site=8
_______________________________________________
Sisuite-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
