On Sun, Mar 16, 2003 at 03:34:17PM +0200, Richard Braakman wrote: > On Sat, Mar 15, 2003 at 10:06:46AM -0700, Bob Proulx wrote: > > Agreed. Note that this is one reason why updating from an older > > released debian version to a newer released debian version should not > > skip intermediate versions. If you do skip major released versions > > then this process to walk a package to a newer version is skipped too. > > Example: Going from potato to sarge, bad, skips steps in process. > > Going from potato to woody then update woody to sarge, good, gets all > > of the right steps. > Isn't this the problem that a combination of Conflicts and Replaces > is supposed to solve? dselect should automatically recommend replacing > the old package with the new package, without any dummy packages being > involved. Not if nothing depends on the new package to automatically pull it in. There are other reasons for conflicts/replaces to be used, which can't be automatically distinguished from "this is an old package"; so to get an automatic upgrade, some package the user already has installed must be changed to depend on the new package. -- Steve Langasek postmodern programmer
Attachment:
pgpo1v_xt7qk4.pgp
Description: PGP signature