X-Git-Url: https://git.saurik.com/apt.git/blobdiff_plain/44477002adb73db2324f4218e5d85aae016ff5fa..bc7a59dded57338e9b5e523726b246dbdd4e0935:/doc/apt_preferences.5.xml?ds=sidebyside diff --git a/doc/apt_preferences.5.xml b/doc/apt_preferences.5.xml index 9d3fc1854..79132e007 100644 --- a/doc/apt_preferences.5.xml +++ b/doc/apt_preferences.5.xml @@ -1,16 +1,9 @@ -%aptent; - - -%aptverbatiment; - - - - + %aptent; + %aptverbatiment; + %aptvendor; ]> @@ -20,7 +13,7 @@ &apt-email; &apt-product; - 2010-02-16T00:00:00Z + 2012-06-09T00:00:00Z @@ -77,7 +70,7 @@ as filename extension and only contain alphanumeric, hyphen (-), underscore (_) and period (.) characters. Otherwise APT will print a notice that it has ignored a file, unless that file matches a pattern in the Dir::Ignore-Files-Silently -configuration list - in this case it will be silently ignored. +configuration list - in which case it will be silently ignored. APT's Default Priority Assignments @@ -122,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 @@ -258,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. @@ -274,7 +275,7 @@ expression surrounded by slashes). Package: gnome* /kde/ -Pin: release n=experimental +Pin: release a=experimental Pin-Priority: 500 @@ -315,30 +316,30 @@ or negative integers. They are interpreted as follows (roughly speaking): -P > 1000 +P >= 1000 causes a version to be installed even if this constitutes a downgrade of the package -990 < P <=1000 +990 <= P < 1000 causes a version to be installed even if it does not come from the target release, unless the installed version is more recent -500 < P <=990 +500 <= P < 990 causes a version to be installed unless there is a version available belonging to the target release or the installed version is more recent -100 < P <=500 +100 <= P < 500 causes a version to be installed unless there is a version available belonging to some other distribution or the installed version is more recent -0 < P <=100 +0 < P < 100 causes a version to be installed only if there is no installed version of the package @@ -346,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: