Differences between version 5 and previous revision of apt_preferences(5).
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 5 | Last edited on Wednesday, March 19, 2003 6:48:50 am | by MishaGorodnitzky | Revert |
| Older page: | version 4 | Last edited on Tuesday, June 4, 2002 12:30:36 am | by perry | Revert |
@@ -51,11 +51,13 @@
followed by an equals then by the string.
Examples:
-v=2.1*,o=Debian,c=main
-l=Debian
-a=stable
+__
v=2.1*,o=Debian,c=main__%%%
+__
l=Debian__%%%
+__
a=stable__%%%
+
+
The data for these matches are taken from the ''Release'' files that APT downloads during an update. The available keys are:
__a= Archive__
@@ -192,11 +194,13 @@
A package pin looks like this:
-Package: apt
-Pin: version .4.
-Pin-Priority: 1001
+__
Package: apt__%%%
+__
Pin: version .4.__%%%
+__
Pin-Priority: 1001__%%%
+
+
The first line specifies the package, the second gives the Pin specification and the last gives the priority of this pin. The first word of the pin specification may be version, release or origin, the remainder of the field is described in the Versioning section above.
A default pin is how the priorities of package files are
@@ -205,11 +209,12 @@
file. Only release or origin may be used in the Pin
specification since they match Packages files.
-Package: *
-Pin: release v=2.1*
-Pin-Priority: 998
+__
Package: *__%%%
+__
Pin: release v=2.1*__%%%
+__
Pin-Priority: 998__%%%
+
If the Pin-Priority field is omitted then the priority defaults to 989 for both cases.
__INTERESTING EFFECTS__
@@ -251,11 +256,11 @@
!!BUGS
See the APT bug page
-/usr/share/doc/debian/bug-reporting.txt'' or the
+''
/usr/share/doc/debian/bug-reporting.txt'' or the
bug(1) command.
!!AUTHOR
APT was written by the APT team
----
