Hal Murray <hmur...@megapathdsl.net>:
>
> j...@systemsartisans.com said:
> > I am in the process of trying to create an RPM package from the repo's
> > current head. Given that I would expect this to be used by sysadmins, etc.
> > who might already have installed the Classic version (very possibly from
> > their distro's package sources), how would you all suggest I treat the
> > presence of a ''conflicting'' version? Save the config files, and
> > overwrite/
> > remove all the old executables? Move everything aside, and put our entire
> > "best practices" package in place?? Ask for manual intervention??? Halt,
> > catch fire, burn it all to the ground? ;)
>
> 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.)
I concur.
We aree going to have a compatibility break when Daniel's new restriction
langage lands, but at that point I expect also to have a tool that will
translate the old configuration language to new one.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
