As a user, I'd be perfectly happy to remove existing NTP packages when I'm going to install beta bits.
On 15/11/2007, at 9:59 AM, Brian Utterback wrote: > The NTP project is about ready for our first beta release, and we > need a > little help with the best way to package it. > > The bits comprise of a few new binaries, replacements for a couple of > old ones, > and man pages. Ideally we would like to deliver the exact same bits > that > will > be in the packages in Nevada, but I am not sure if that is feasible. > > What is the effect of installing a new package that has conflicting > bit > from a > previous package? And if it is okay to install it that way, can the > package be > removed and things put back the way they were before? > > Would it make sense to ask users to remove the existing ntp packages > before > installing the new ones? If so, what would be the best method to > reinstall? > Obviously that would be sub-optimal. In addition, there would still > be the > man page conflicts. > > Perhaps a pre-install script that would removef the conflicting files > from their respective packages and then a post-remove script to > intallf them back? > > Any ideas or suggestions? > > Brian Utterback > _______________________________________________ > ntp-discuss mailing list > ntp-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ntp-discuss >
