Re: New dpkg upload - please test!

[Santiago Vila <sanvila@unex.es>]

On Thu, 14 Oct 1999, Wichert Akkerman wrote:

> Previously Wichert Akkerman wrote:
> > dpkg (1.4.1.15) unstable; urgency=low
> > 
> >   * non-maintainer release.
> >   * Move dselect into its own package
> 
> Oops, I forgot to remove this from the changelog. I reverted this change
> since there is no good upgrade strategy for moving dselect to another
> package.
> 
> The problem is that when you upgrade the dpkg package it will remove
> dselect. dselect will only return when the new dselect package is installed.
> This means there is a timeframe in which you might be doing an install
> using dselect during which dselect removes itself. This can produce quite
> nasty problems; imagine what would happen if the install fails before the
> dselect package gets installed...
> 
> The only way I can see to prevent this is to rename the dpkg package, and
> make dpkg a dummy-package that Pre-Depends on dselect and the new dpkg package.
> That will enforce that both dpkg and dselect will be installed when you
> upgrade your system.

Would not be possible to make the new dpkg to pre-depend on the new
dselect?

This way, the new dselect would replace the dselect-inside-the-dpkg-package
first, and then dpkg would be upgraded without removing dselect.

Thanks.

-- 
 "b2c21d8c3060f92905c94135c37906f1" (a truly random sig)