Path: utzoo!attcan!uunet!snorkelwacker!usc!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!hub.ucsb.edu!ucsbuxa!3003jalp
From: 3003jalp@ucsbuxa.ucsb.edu (Applied Magnetics)
Newsgroups: comp.unix.admin
Subject: Re: Software installation opinions needed
Message-ID: <6340@hub.ucsb.edu>
Date: 24 Sep 90 21:24:41 GMT
References: <25908@shamash.cdc.com> <1990Sep19.144819.12179@dg-rtp.dg.com> <MOORE.90Sep21091732@terra.srl.mew.mei.co.jp>
Sender: news@hub.ucsb.edu
Lines: 16


If your package must be installed by root, do this:
 1) Install via a script with lots of comments.  This way, the system
    administrator can examine the script and change it if he wants to.
    A script is better than a makefile, say, because it can be read
    from top to bottom.
 2) If things are just too complicated, the script can be generated
    by a separate configuration script/makefile/binary.  Or some set
    of actions may be performed by a preliminary
    script/makefile/binary.  The rule here should be:  everything is
    completely innocuous until the final script is run by root.
 3) As a part of final installation, generate a manifest of all files,
    links etc. and their owner, group and final resting place.  Let the
    administrator decide where to keep the manifest.

--Pierre Asselin, Applied magnetics Corp.