On Fri, May 19, 2006 at 05:54:07PM +0200, Frank Küster wrote: > Christoph Haas <haas@debian.org> wrote: > > > This is done by removing all files from the package B and setting > > the dependencies as follows: > > > > A: > > > > Replaces: B > > Conflicts: B > > > > B: > > > > Depends: A > > Description: Transitional package for A > > This is a transitional package which ensures users of B will use > > A in the future. It can safely be removed. > > How can that work? If B Depends: A, but A Conflicts: B, won't they just > refuse to be upgraded? I think A needs to declare > Conflicts: B ( <= $last_nontransitional_version ). I think you are closer to the real solution. In #debian-devel people just suggested that a "B: depends on A" is the only thing the transitional package needs. This way both will be installed if just B was installed. And after the next stable release B can safely be removed because users of B will have A installed, too. Is this worth a few bytes in the policy? :) Kindly Christoph -- ~ ~ ".signature" [Modified] 1 line --100%-- 1,48 All
Attachment:
signature.asc
Description: Digital signature