home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sgi.misc
- Path: sparky!uunet!stanford.edu!nntp.Stanford.EDU!dhinds
- From: dhinds@leland.Stanford.EDU (David Hinds)
- Subject: Re: making inst distributions (was: Re: ghostscript)
- Message-ID: <1993Jan9.081614.6675@leland.Stanford.EDU>
- Sender: news@leland.Stanford.EDU (Mr News)
- Organization: DSG, Stanford University, CA 94305, USA
- References: <1il5f4INN6pq@fido.asd.sgi.com> <1993Jan9.023523.861@leland.Stanford.EDU> <1ilp7jINNioq@fido.asd.sgi.com>
- Date: Sat, 9 Jan 93 08:16:14 GMT
- Lines: 28
-
- In article <1ilp7jINNioq@fido.asd.sgi.com> pj@sgi.com writes:
- >In article <1993Jan9.023523.861@leland.Stanford.EDU>, dhinds@leland.Stanford.EDU (David Hinds) writes:
- >|> [[ omitted: use of "versions" to list config files. ]]
- >}> But this still leaves out a few system files
- >|> that I've changed but which are not known to inst as configuration
- >|> files. These will still get clobbered when I upgrade IRIX, and I
- >|> will have to keep track of them on my own.
- >
- >1. Let me play back what I understand you to be saying.
- >
- > If you have intentionally modified a normal inst'ed file, a
- > file not known as a config file to inst, then you would like
- > to tell inst, to treat this file as if it were a config
- > file:
- >
- > * naming upgrade versions with a .N suffix,
- > * listing that file in the output of "versions changed",
- > * giving you a chance to merge in your localisms, and
- > * letting you list all config files, for cloning systems.
-
- Yes, yes, yes, and yes! I understand that it might be necessary to
- install the upgrade versions of these files to guarantee that the OS
- can function, so the default could be to rename the user-modified
- files to the .O suffix. But this is just what I'd like. Maybe the
- extra "config" names could be read from a text file in /usr/lib/inst.
-
- - David Hinds
- dhinds@allegro.stanford.edu
-