PACMAN.CONF(5) | Pacman Manual | PACMAN.CONF(5) |
NAME
pacman.conf - pacman package manager configuration fileSYNOPSIS
/etc/pacman.confDESCRIPTION
Pacman, using libalpm(3), will attempt to read pacman.conf each time it is invoked. This configuration file is divided into sections or repositories. Each section defines a package repository that pacman can use when searching for packages in --sync mode. The exception to this is the options section, which defines global options.Comments are only supported by beginning a line with the hash (#) symbol. Comments cannot begin in the middle of a line.
EXAMPLE
# # pacman.conf # [options] NoUpgrade = etc/passwd etc/group etc/shadow NoUpgrade = etc/fstab [core] Include = /etc/pacman.d/core [custom] Server = file:///home/pkgs
Note
Each directive must be in CamelCase. If the case isn’t respected, the directive won’t be recognized. For example. noupgrade or NOUPGRADE will not work.
OPTIONS
RootDir = /path/to/root/dirDBPath = /path/to/db/dir
CacheDir = /path/to/cache/dir
HookDir = /path/to/hook/dir
GPGDir = /path/to/gpg/dir
LogFile = /path/to/log/file
HoldPkg = package ...
IgnorePkg = package ...
IgnoreGroup = group ...
Include = /path/to/config/file
Architecture = auto | i686 | x86_64 | ...
XferCommand = /path/to/command %u
This option is useful for users who experience problems with built-in HTTP/FTP support, or need the more advanced proxy support that comes with utilities like wget.
NoUpgrade = file ...
NoExtract = file ...
CleanMethod = KeepInstalled &| KeepCurrent
SigLevel = ...
LocalFileSigLevel = ...
RemoteFileSigLevel = ...
UseSyslog
Color
TotalDownload
CheckSpace
VerbosePkgLists
DisableDownloadTimeout
REPOSITORY SECTIONS
Each repository section defines a section name and at least one location where the packages can be found. The section name is defined by the string within square brackets (the two above are core and custom). Repository names must be unique and the name local is reserved for the database of installed packages. Locations are defined with the Server directive and follow a URL naming structure. If you want to use a local directory, you can specify the full path with a “file://” prefix, as shown above.A common way to define DB locations utilizes the Include directive. For each repository defined in the configuration file, a single Include directive can contain a file that lists the servers for that repository.
[core] # use this server first Server = ftp://ftp.archlinux.org/$repo/os/$arch # next use servers as defined in the mirrorlist below Include = {sysconfdir}/pacman.d/mirrorlist
The order of repositories in the configuration files matters; repositories listed first will take precedence over those listed later in the file when packages in two repositories have identical names, regardless of version number.
Include = path
Server = url
During parsing, pacman will define the $repo variable to the name of the current section. This is often utilized in files specified using the Include directive so all repositories can use the same mirrorfile. pacman also defines the $arch variable to the value of Architecture, so the same mirrorfile can even be used for different architectures.
SigLevel = ...
Usage = ...
Sync
Search
Install
Upgrade
All
Note that an enabled repository can be operated on explicitly, regardless of the Usage level set.
PACKAGE AND DATABASE SIGNATURE CHECKING
The SigLevel directive is valid in both the [options] and repository sections. If used in [options], it sets a default value for any repository that does not provide the setting.Alternatively, you can get more fine-grained control by combining some of the options and prefixes described below. All options in a config file are processed in top-to-bottom, left-to-right fashion, where later options override and/or supplement earlier ones. If SigLevel is specified in a repository section, the starting value is that from the [options] section, or the built-in system default as shown below if not specified.
The options are split into two main groups, described below. Terms used such as “marginally trusted” are terms used by GnuPG, for more information please consult gpg(1).
When to Check
Never
Optional (default)
Required
What is Allowed
TrustedOnly (default)
TrustAll
Options in both groups can additionally be prefixed with either Package or Database, which will cause it to only take effect on the specified object type. For example, PackageTrustAll would allow marginal and unknown trust level signatures for packages.
The built-in default is the following:
SigLevel = Optional TrustedOnly
USING YOUR OWN REPOSITORY
If you have numerous custom packages of your own, it is often easier to generate your own custom local repository than install them all with the --upgrade option. All you need to do is generate a compressed package database in the directory with these packages so pacman can find it when run with --refresh.repo-add /home/pkgs/custom.db.tar.gz /home/pkgs/*.pkg.tar.gz
The above command will generate a compressed database named /home/pkgs/custom.db.tar.gz. Note that the database must be of the form defined in the configuration file and {ext} is a valid compression type as documented in repo-add(8). That’s it! Now configure your custom section in the configuration file as shown in the config example above. Pacman will now use your package repository. If you add new packages to the repository, remember to re-generate the database and use pacman’s --refresh option.
For more information on the repo-add command, see “repo-add --help” or repo-add(8).
SEE ALSO
pacman(8), libalpm(3)See the pacman website at https://www.archlinux.org/pacman/ for current information on pacman and its related tools.
BUGS
Bugs? You must be kidding; there are no bugs in this software. But if we happen to be wrong, submit a bug report with as much detail as possible at the Arch Linux Bug Tracker in the Pacman section.AUTHORS
Current maintainers:Past major contributors:
For additional contributors, use git shortlog -s on the pacman.git repository.
2020-06-25 | Pacman 5.2.2 |