Template:Article summary start Template:Article summary text Template:Article summary heading Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary end
The pacman package manager is one of the main features of Arch Linux. It combines a simple binary package format with an easy-to-use build system (see makepkg and Arch Build System). The goal of pacman is to make it possible to easily manage packages, whether they are from the official Arch repositories or the user's own builds.
pacman keeps the system up to date by synchronizing package lists with the master server. This server/client model also allows you to download/install packages with a simple command, complete with all required dependencies.
pacman is written in the C programming language. It uses the .tar.gz package format, in an effort to further enhance its speed; Gzipped tarballs, though slightly larger, are decompressed much faster than their Bzipped counterparts, and are therefore generally installed more expediently.
- 1 Configuration
- 2 Usage
- 3 Troubleshooting
- 4 Further reading
- 5 External links
pacman configuration is located in Template:Filename. This is the place where the user configures the program to work in the desired manner. In depth information about the configuration file can be found in man pacman.conf.
Skip package from being upgraded
To skip upgrading a specific package, add it to the pertinent section:
Skip package group from being upgraded
As with packages, skipping a whole package group is also possible:
This section defines which repositories to use, as referred to in Template:Filename. They can be stated here directly, or included from another file.
[core] # Add your preferred servers here, they will be used first Include=/etc/pacman.d/mirrorlist [extra] # Add your preferred servers here, they will be used first Include=/etc/pacman.d/mirrorlist [community] # Add your preferred servers here, they will be used first Include=/etc/pacman.d/mirrorlist
To read other examples of what pacman can do, refer to man pacman. The examples below are just a small sample of operations that can be performed.
To install a single package or list of packages (including dependencies), issue the following command:
# pacman -S package_name1 package_name2
Sometimes there are multiple versions of a package in different repositories (e.g. extra and testing). Specify which one to install:
# pacman -S extra/package_name # pacman -S testing/package_name
To remove a single package, leaving all of its dependencies installed:
# pacman -R package_name
To remove a package's dependencies which are not required by any other installed package:
# pacman -Rs package_name
pacman saves important configuration files when removing certain applications and names them with the extension: Template:Filename. To delete these backup files use the -n option:
# pacman -Rn package_name # pacman -Rns package_name
pacman can update all packages on the system with just one command. This could take quite a while depending on how up-to-date the system is. The best option is to synchronize the repository databases and update the system in one go, with the following:
# pacman -Syu
pacman is a powerful package management tool, but it does not attempt to "do everything", as it were. Read The Arch Way if this confuses you. Rather, users must be vigilant and take responsibility for maintaining their own system. When performing a system update (Template:Codeline), for example, it is essential that users read all information output by pacman and use common sense.
For example, if Template:Codeline is to be updated to a new minor version, the cautious user immediately recognizes that packages that include kernel modules (such as Template:Codeline and Template:Codeline) must be updated/rebuilt as well. If a Template:Codeline update is available, but no updates are yet available for Template:Codeline, it is not recommended to update Template:Codeline unless willing to deal with Template:Codeline breaking!
This is not a problem unique to Arch Linux, per se; kernel modules must be built against the running kernel. However, fixed-release distributions usually ensure that kernel updates are accompanied with updates to all "affected" packages. As a cutting-edge rolling-release distribution, kernel updates are available immediately in Arch Linux. "Affected" packages are usually updated within a matter of hours of a kernel update, but may not be available until your repositories are synced. Always use common sense!
Another example: during an update, pacman indicates that a new version of Template:Codeline is available. The update changes input device handling -- X will not start afterwards without user intervention; changes to Template:Filename are necessary. However, without fail, dozens of forum threads are opened after the update is released by users unable to start X.
Instead of immediately updating as soon as updates are available, users must recognize that an update to Template:Codeline may cause X not to start afterwards. This means that is not wise to update Template:Codeline if one is about to deliver an important presentation, for example. Rather, update during free time and be prepared to deal with any problems that may arise due to the update.
Next, a visit to the Arch Linux home page is always warranted. In this example, a news item was posted regarding the update which linked to a ArchWiki page that described how to reconfigure X. Often when updates to "critical" packages require user intervention, an appropriate update to http://archlinux.org will be made. Normally there will be forum posts describing the very same issue shortly after the update becomes available across the mirrors, detailing the solution any "problems".
When the actual update is performed, be sure to read the messages printed out by pacman. Packagers often describe the changes and the expected problems, and direct the users to the appropriate ArchWiki page. Always read all information output by pacman!
Querying package databases
pacman queries the local package database with the -Q flag; see:
$ pacman -Q --help
and queries the sync databases with the -S flag; see:
$ pacman -S --help
pacman can search for packages in the database, searching both in packages' names and descriptions:
$ pacman -Ss package
To search for already installed packages:
$ pacman -Qs package
To display extensive information about a given package:
$ pacman -Si package
for locally installed packages:
$ pacman -Qi package
To retrieve a list of the files installed by a package:
$ pacman -Ql package
One can also query the database to know which package a file on the file system belongs to.
$ pacman -Qo /path/to/a/file
To list all packages no longer required as dependencies (orphans):
$ pacman -Qdt
Download a package without installing it:
# pacman -Sw package
Install a 'local' package that is not from a repository:
# pacman -U /path/to/package/package_name-version.pkg.tar.gz
Install a 'remote' package (not from a repository):
# pacman -U http://www.examplepackage/repo/examplepkg.tar.gz
Clean the package cache of packages that are not currently installed (/var/cache/pacman/pkg):
# pacman -Sc
Clean the entire package cache:
# pacman -Scc
- Pacman Tips
- Pacman GUI Frontends
- Improve Pacman Performance
- Downgrading Packages
- Arch User Repository
- Local Mirror
- Pacman Rosetta