[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Rule-list] Install using extra_packages and a post install script.
From: |
hairylarry |
Subject: |
[Rule-list] Install using extra_packages and a post install script. |
Date: |
Fri, 12 Apr 2002 00:21:38 -0500 |
Using Extra Packages and Slinky post install scripts.
To add Midnight Commander to the slinky install place these three
files in the second_stage_scripts directory of slinky disk 2.
extra_packages
mc-4.5.51-36.i386.rpm.post.sh
mc.menu
Slinky reads the extra_packages file which contains just the name of
the Midnight Commander rpm file on Redhat CD 1, mc-4.5.51-
36.i386.rpm.
After it installs Midnight Commander it finds the post install script
and runs it. (Slinky also tests for pre install scripts)
The post install script copies mc.menu to /root/.mc.menu installing a
menu in the root directory. This is meant as an example only. I don't
think it is the best way to handle Midnight Commander menus.
Slinky copies all files in the second_stage_scripts directory to
/boot/scripts before it installs the rpms. The final script in the Slinky
install deletes this directory. But whatever you want to put there will
be available to your scripts. Of course, subject to disk space. But
this is an excellent way to move configuration files in as part of a
Slinky install.
I also suggest that we add an option to run a post install script, say
rulerc.sh, if it were present. This would allow Slinky configurers a
final chance at tweaking setup files that may not be related to a
specific rpm.
Slinky Version 0.1.9a. Tested on PC 14, a 166 pentium with 32 meg
ram and a 540 meg hard drive.
Thanks,
Hairy Larry
- [Rule-list] Install using extra_packages and a post install script.,
hairylarry <=