question about upgrading from Classic to NTPsec (packaging issue)

Eric S. Raymond esr at
Mon Jul 4 10:41:59 UTC 2016

Hal Murray <hmurray at>:
> JDB at 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="">Eric S. Raymond</a>

More information about the devel mailing list