X-Git-Url: https://git.saurik.com/apt.git/blobdiff_plain/5abbf5bbb5ee8717f89cac6ef409c4cec79259f6..c3c3bd043b262dd5544594abd5e5bd4377a679d6:/doc/apt_preferences.5.xml
diff --git a/doc/apt_preferences.5.xml b/doc/apt_preferences.5.xml
index 16e6a7aa0..513a0c135 100644
--- a/doc/apt_preferences.5.xml
+++ b/doc/apt_preferences.5.xml
@@ -13,7 +13,7 @@
&apt-email;
&apt-product;
- 2012-06-09T00:00:00Z
+ 2015-08-15T00:00:00Z
@@ -115,14 +115,17 @@ from archives which in their Release files are marked as "N
priority 500
-to the versions that are not installed and do not belong to the target release.
+to the versions that do not belong to the target release.
priority 990
-to the versions that are not installed and belong to the target release.
+to the versions that belong to the target release.
+
+The highest of those priorities whose description matches the version is assigned to the
+version.
If the target release has not been specified then APT simply assigns
@@ -251,6 +254,11 @@ Pin-Priority: 500
+
+The effect of the comma operator is similar to an "and" in logic: All
+conditions must be satisfied for the pin to match. There is one exception:
+For any type of condition (such as two "a" conditions), only the last such
+condition is checked.
@@ -267,7 +275,7 @@ expression surrounded by slashes).
Package: gnome* /kde/
-Pin: release n=experimental
+Pin: release a=experimental
Pin-Priority: 500
@@ -339,14 +347,21 @@ only if there is no installed version of the package
P < 0
prevents the version from being installed
+
+P = 0
+has undefined behaviour, do not use it.
+
-If any specific-form records match an available package version then the
-first such record determines the priority of the package version.
-Failing that,
-if any general-form records match an available package version then the
-first such record determines the priority of the package version.
+
+The first specific-form record matching an available package version determines
+the priority of the package version.
+Failing that, the priority of the package is defined as the maximum of all
+priorities defined by generic-form records matching the version.
+Records defined using patterns in the Pin field other than "*" are treated like
+specific-form records.
+
For example, suppose the APT preferences file contains the three
records presented earlier: