Hal Murray via devel writes:
> What's going to happen if a distro packages up our stuff and somebody
> wants to install both our code and ntp classic?
Well if a distro packages both NTP classic and NTPsec, then they would
either:
1) Mark them in their repos as mutually incompatible so you can ins
ernatives" in which case the package
system has logic to prevent them from being installed at the same
time.
the ntpsec-vs-Classic name clash is not even a particularly
exceptional situation - there gave been forks of base utilities
before. There are, for example, a couple of different
implementar
> That works only because we install in /usr/local/ while the system
version of
> ntp classic gets installed in /usr/ What's going to happen if a distro
> packages up our stuff and somebody wants to install both our code and ntp
> classic?
For a distro, like Debian, the new package would be calle
We have ntpd and ntpq that replace the programs with the same names from ntp
classic.
For testing, we install in /usr/local/ so we don't conflict with a system
version of ntp classic. If you hack your search path, you get our code
rather than the system programs with the same names.
That wor
