John D. Bell <j...@systemsartisans.com>:
> Do we want to install NTPsec in the same hierarchy as Classic? Or in an
> alternative location? (/usr/local? /opt??)
Same hierarchy. The last thing we want is bug reports due to an accidentally
mixed installation...
> So far, the config files are compatible so it makes sense to leave the old
> > one alone if it has been edited. (The admin might have picked some good
> > servers or setup logging.)
> >
>
> Yes. Another method is to do like a standard RPM upgrade script does, and
> only clobber the existing config file *if* it is unchanged from the last
> version's
> distributed version. Any changes cause the new config file to be dropped
> into the directory with a "-rpmnew" suffix. Then the admin has to resolve
> conflicts manually.
+1
> > Where would you document what happened and/or how to switch back?
>
>
> Good question. Suggestions?
Some documentation file in /usr/share/ntpsec - READNE-UPGRADE or
something.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
