Path: utzoo!attcan!uunet!aplcen!samsung!know!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!olivea!orc!inews!iwarp.intel.com!gargoyle!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.unix.admin
Subject: Re: categories of files (was Re: Software installation opinions needed)
Message-ID: <1990Sep26.210617.12193@chinet.chi.il.us>
Date: 26 Sep 90 21:06:17 GMT
References: <1990Sep19.144819.12179@dg-rtp.dg.com> <26645@mimsy.umd.edu> <1990Sep26.043825.26682@maytag.waterloo.edu>
Organization: Chinet - Chicago Public Access UNIX
Lines: 20

In article <1990Sep26.043825.26682@maytag.waterloo.edu> gamiddle@maytag.waterloo.edu (Guy Middleton) writes:

>We have a very grandiose software installation doctrine here, and tend to
>subdivide yet further, into these categories:

The initial installation of a particular package is rarely a difficult
problem because at that point the rest of the system is likely to
be fairly stable and the installer can concentrate on the changes this
particular package is making.

The difficult part comes when (a) you upgrade the OS and the package
touches some of the base system files (perhaps replacing /bin/mail
with something reasonable on a sysV machine or the like) or (b) you
want to move a package in its current state to a different machine
(keeping initialized data files, etc.). How do you tell which
pieces belong to which package, and in what order to reconstruct
things?  

Les Mikesell
 les@chinet.chi.il.us