> 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 called "ntpsec", and marked as conflicting with ntp. So installing ntpsec would remove ntp. Namespace clashes would not occur. -- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane On Sat, Feb 17, 2018 at 6:08 AM, Hal Murray via devel <[email protected]> wrote: > > 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 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? > > How do other projects with similar name clashes handle things? > > Are we setting ourselves up for problems tomorrow by hijacking the names to > make things convenient today? > > There are similar problems with man pages. Probably others that I can't > think of right now. > > > -- > These are my opinions. I hate spam. > > > > _______________________________________________ > devel mailing list > [email protected] > http://lists.ntpsec.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list [email protected] http://lists.ntpsec.org/mailman/listinfo/devel
