PackageDependencyFixes

Differences between revisions 2 and 11 (spanning 9 versions)
⇤ ← Revision 2 as of 2005-10-24 23:07:46 →
Size: 3004
Editor: 200
Comment:
← Revision 11 as of 2008-08-06 16:32:11 → ⇥
Size: 497
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 * '''Launchpad Entry''': https://launchpad.net/distros/ubuntu/+spec/
 * '''Created''': [[Date(2005-10-18T16:44:35Z)]] by IanJackson3
 * '''Contributors''': IanJackson3
 * '''Packages affected''': 		This specification has been split in two.
Line 8: Line 5:
== Summary == New specs and LP pages:
 * https://wiki.ubuntu.com/PackageDependencyFieldBreaks
 * https://launchpad.net/distros/ubuntu/+spec/package-dependency-field-breaks
 * https://wiki.ubuntu.com/ReplacementPackageAutoInstallation
 * https://launchpad.net/distros/ubuntu/+spec/replacement-package-auto-installation
Line 10: Line 11:
Two fixes to the dependency management system in dpkg, apt and higher layers: Implement Breaks, and implement the correct selection behaviour for Replaces.

== Rationale ==

Correct behaviour in the presence of Replaces will allow us to get rid of all `transitional packages'. These are effort to create and maintain and of course cause confusion and cruft.

Breaks will replace almost every use of Conflicts << without Replaces <<. This will reduce the amount of churn needed during upgrades, as packages will no longer need to be removed. Installation ordering will be less criticial. This will make upgrades less fragile. In particular, it should eliminate most semi-accidental removals implied by the dependency system, and switching routine use to the less-dangerous Breaks will reduce the total amount of damage done by incorrect dependencies. It may also speed up upgrades.

== Use cases ==

Breezy i386 contains 909 instances of Conflicts << in main; 1921 overall. There is scope for considerable improvement here - Breaks would get rid of nearly all of these.

Breezy i386 contains around 18-29 transitional packages which could be simply abolished. With proper behaviour on Replaces, transitional packages will no longer be required when package names change.

== Scope ==

dpkg and apt and other programs which read/write status files need to be taught about Breaks so as not to mind it.

dpkg needs to be taught how to apply Breaks (usually, deconfigure packages if necessary).

apt does not need to consider Breaks although it might be useful to try to minimise the aforementioned deconfiguration.

dselect and apt need to be taught about the full meaning of Replaces.

== Design ==

Breaks:
http://www.dpkg.org/Breaks
http://lists.debian.org/debian-devel/1997/10/msg00643.html

Replaces: when A is selected by the user for installation, and a newly-available package B appears such that (the new version of) B Replaces (the current version of) A, then B should automatically be marked as selected for installation. This is in addition to the other behaviours of Replaces. See http://lists.debian.org/debian-devel/2005/06/msg02045.html, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=47540. This has been a planned intended behaviour of Replaces for some time, as old versions of the Debian Packaging manual show.

== Implementation ==

=== Code ===

=== Data preservation and migration ===

Not relevant.

== Outstanding issues ==

== BoF agenda and discussion ==

LeonardoSantagada: Maybe you should think about using SmartPM(http://www.smartpm.org/), it will not fix all of the problems but it is easier to replace synaptic than to fix dpkg and apt in my opinion.		 Old LP page:
 * https://launchpad.net/distros/ubuntu/+spec/package-dependency-fix (old LP page)

This specification has been split in two.

New specs and LP pages:

Old LP page:

PackageDependencyFixes (last edited 2008-08-06 16:32:11 by localhost)