On Sat, Apr 05, 2003 at 11:41:07PM +0200, Andreas Metzler wrote: > Andrew Suffield <asuffield@debian.org> wrote: > > On Sat, Apr 05, 2003 at 04:48:58PM +0200, Andreas Metzler wrote: > >> Andrew Suffield <asuffield@debian.org> wrote: > >> > On Sat, Apr 05, 2003 at 11:22:54AM +0200, Andreas Metzler wrote: > >> >> Currently the exim4-packages cannot provide /usr/sbin/exim (only > >> >> /usr/sbin/exim4) because exim v3's init script up to version 3.36-4 > >> >> uses something aequivalent to this to check whether it should do > >> >> anything: [ -x /usr/sbin/exim ] || exit. If you had exim v3 > >> >> uninstalled (but not purged) and installed exim v4 and it contained > >> >> /usr/sbin/exim both init-scripts would try to run a daemon. The same > >> >> applies to the cron-snippets. > > >> >> The exim3 init script in sid has already been changed to use another > >> >> test that recognizes exim v3 properly but this doesn't help the users > >> >> who will upgrade from woody to sarge (when it is stable), switching > >> >> directly to exim v4 without installing eximv3 from sarge first. > > >> > Conflicts: exim (<< 3.36-4) > > >> init script and cron-snippets are conffiles and "Conflicts" only > >> guarantees uninstall but not purge. > > > Oh, you're not trying to get them both to install at once? > > Replaces: exim, and have /etc/init.d/exim in both. You'll get standard > > conffile handling. > > I want them as separate packages, to keep this functionality: > 1 running exim3 > 2 apt-get install exim4 > 3 test exim4, doesn't like it > 4 apt-get install exim > 5 exim v3 runs again. A Replaces directive and the same file in both would appear to be the wya to go, then; it'll do what you just said. Plus, if the local admin edits the init script in the meantime, they'll get the standard message for conflicting conffile changes. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | Dept. of Computing, `. `' | Imperial College, `- -><- | London, UK
Attachment:
pgpgm1Os1P3ub.pgp
Description: PGP signature