I would require all ntp related packages to be removed as a preinstall action. My only concern would be backing up the config files. Are they compatible between the two versions?
-Brian On Nov 14, 2007 5:59 PM, Brian Utterback <Brian.Utterback at sun.com> 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 > -- - Brian Gupta http://opensolaris.org/os/project/nycosug/
