Bug#240665: [PROPOSAL] require depending on split-off packages
On Sun, 28 Mar 2004, Andreas Barth wrote:
>
> 7.5.3 Moving files or functionality to another package
>
> If some functionality is moved from one package to another (also at
> splitting off a package), the first one must depend on the second
> for the time of at least one stable release. By this, no
> functionality is removed on dist-upgrade.
This is broken because it eliminates one of the points of splitting
the packages in the first place.
That is, no one can have only one of the packages installed. [Think
about a foo and a foo-doc split.]
The appropriate level of (Depends:, Recommends:, Suggests:) is
dependant on the package itself, and frankly, the maintainer is
(hopefully!) the best person to determine that.
I'd have no problem with sticking similar language that forms a
recommendation rather than a requirement though. [But that probably
should go in the developer's reference.]
Don Armstrong
--
Any excuse will serve a tyrant.
-- Aesop
http://www.donarmstrong.com
http://rzlab.ucr.edu
Reply to: