🚀 go-pugleaf

In article <1993Jan8.150400.20212@eagle.lerc.nasa.gov>, tohanson@gonzo.lerc.nasa.gov (Jeff Hanson) writes:
|> It would be nice if administrators could add
|> files to the list that inst has of configuration files.  This way we can
|> use inst to control our configurations as well as those SGI supports.

I'm not sure I understand this.

Are you hoping that "versions changed" would emit names of your
other config files that have changed (ie - have file.N or file.O
variants visible)?  Nah - that doesn't sound right - and I'm at a
loss for other guesses.

The point of inst's idea of config files is to avoid inst'ing
over the top of a previously inst'ed file, when that previous
version has been changed since it was inst'ed, and we presume
that you might want to preserve or merge the changes with our new
version.

So for files that you obtained by means other than inst'ing
software, I don't see what gain you have in mind.

-- 

				I won't rest till it's the best ...
				Software Production Engineer
				Paul Jackson (pj@sgi.com), x1373