[Rule-list] Pre and post install scripts

[Marco Fioretti]

Martin, Devon

the more I think about your suggestion and the way Devon implemented
it, the more I like the idea. I, too, don't know exactly how many
practical uses we could find for it (apart from the very useful disk
space recovery, of course), but am sure that there are many others.

For example, this hook for pre/post install scripts sounds like
something we could use to do highly customized install and slinky
based *upgrades*, doesn't it? The scripts may be used to place on disk
your existing dial-up parameters, or to maintain current config
files.. etc..

        Ciao,
                Marco Fioretti
                RULE project leader  

On Tue, Apr 02, 2002 22:28:43 at 10:28:43PM -0500, Devon wrote:
> On Tuesday 02 April 2002 10:31 am, Martin Stricker wrote:
> 
> > installation. Since we do not want to repackage the RPMs (I fully
> > second that!) we cannot do this in the RPM post-install script.
> > Therefore we need additional post-install scripts for eack package
> > which has huge i18n-files. I guess they have to be located on yet
> > another floppy, 
> 
> There is plenty of room on the miniconda updates disk, as well as slinky 
> disk 2 for scripts of this nature.
> 
> > and in the install script in the RPM installation loop
> > there has to be something like
> > if -f /path/to/scripts/$packagename.sh
> >     /path/to/scripts/$packagename.sh
> > fi
> 
> I like this. Enough that I added it to Slinky already. :)
> As each package is installed, the installer looks for a file named 
> $package.post.sh and executes it, if it exists.
> This also gives us the possibility of executing our own pre-install 
> scripts via a file named $package.pre.sh. I don't know that we need the 
> pre-install portion, but it's available if need be.
> 

-- 
The three most dangerous things are a programmer with a soldering
iron, a manager who codes, and a user who gets ideas.