|
Kali Linux Revealed
Pdf ko'rish
|
| bet | 120/174 | | Sana | 15.01.2024 | | Hajmi | 11,68 Mb. | | #137314 |
Bog'liq Kali-Linux-Revealed-2021-editionPriority of Debian
Experimental
If you listed Debian experimental in your
sources.list
file, the corresponding pack-
ages will almost never be installed because their default APT priority is 1. This
is of course a specific case, designed to keep users from installing experimental
packages by mistake. The packages can only be installed by typing
apt install
package/experimental
, assuming of course that you are aware of the risks and po-
tential headaches of life on the edge. It is still possible (though
not
recommended)
to treat packages of experimental like those of other distributions by giving them a
priority of 500. This is done with a specific entry in
/etc/apt/preferences
:
Package: *
Pin: release a=experimental
Pin-Priority: 500
Let’s suppose that you only want to use packages from Kali and that you only want Debian pack-
ages installed when explicitly requested. You could write the following entries in the
/etc/apt/
preferences
file (or in any file in
/etc/apt/preferences.d/
):
Package: *
Pin: release o=Kali
Pin-Priority: 900
Package: *
Pin: release o=Debian
Pin-Priority: -10
In the last two examples, you have seen a=experimental, which defines the name of the selected
distribution and o=Kali and o=Debian, which limit the scope to packages whose origin are Kali and
Debian, respectively.
Let’s now assume that you have a server with several local programs depending on the version 5.22
of Perl and that you want to ensure that upgrades will not install another version of it. You could
use this entry:
Package: perl
Pin: version 5.22*
Pin-Priority: 1001
The reference documentation for this configuration file is available in the manual page
apt_preferences(5)
, which you can display with
man apt_preferences
.
203
Chapter 8 — Debian Package Management
|
| |
