Path: utzoo!attcan!uunet!sugar!peter From: peter@sugar.uu.net (Peter da Silva) Newsgroups: comp.sys.amiga Subject: Re: S/W Installation methodology Message-ID: <3146@sugar.uu.net> Date: 23 Dec 88 22:43:33 GMT References: <3128@sugar.uu.net> <896@quintus.UUCP> Organization: Sugar Land Unix - Houston, TX Lines: 14 In article <896@quintus.UUCP>, pds@quintus.uucp (Peter Schachte) writes: > This sounds like a good principle, but you still haven't said what > installation should *do*. It should put the names of the various files and directories in a file in s: (if text). The name of this file should be chosen to avoid conflicts, but it should be otherwise unrestricted. I would suggest '*.configuration', where * is the name of the program. Then it should tell the user what it's done so they can copy it to a more appropriate place (like, df0:s) if s: is in a RAM disk. If the file does not exist, the installation should be run again. -- Peter "Have you hugged your wolf today" da Silva `-_-' peter@sugar.uu.net