Proposal: `Breaks:' field.
- To: Debian Developers <firstname.lastname@example.org>
- Subject: Proposal: `Breaks:' field.
- From: Santiago Vila Doncel <email@example.com>
- Date: Wed, 19 Feb 1997 16:28:00 +0100 (MET)
- Message-id: <Pine.LNX.3.95.970219160423.675A-100000@cantor>
-----BEGIN PGP SIGNED MESSAGE-----
This morning I installed bash 2.0. This afternoon, when booting, I saw a
strange message produced by one of the rc2.d scripts...
I think that the packaging system should be able to avoid this, and
currently it is not (Am I right?). That's why a propose a new control
header field: Breaks:
Breaks: would be like Pre-depends: but in *reverse* way.
i.e. bash 2.0 may have in its control file something like this:
Breaks: something <= foo-version, anotherthing <= bar-version, etc.
This way, dpkg would refuse to install bash 2.0 if you have any of these
dselect should treat this "Breaks" as a reverse Depend: but only if you
really have the broken package already installed.
For example, if "package A" breaks "B version <= foo" then dselect will
upgrade package B before upgrading package A. But it should not worry
about if package B is not even installed.
The most important thing here is to ensure that the system is always
stable, and that we do not risk system's integrity.
Don't we need this new field?
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
Santiago Vila <firstname.lastname@example.org>
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com