Difference between revisions of "Pacman"
m (→Removing packages)
m (Remove all the orphan packages)
|Line 195:||Line 195:|
# pacman -Scc
# pacman -Scc
== Troubleshooting ==
== Troubleshooting ==
Revision as of 07:44, 6 June 2011
Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary heading Template:Article summary link Template:Article summary link Template:Article summary link Template:Article summary link 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 and uses the Template:Filename package format.
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, specify it as such:
For multiple packages use a space.
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 and its 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. This command can synchronize the repository databases and update the system's packages:
# 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.
Instead of immediately updating as soon as updates are available, users must recognize that an update to a critical package may have unforeseen consequences. 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. Often when updates require user intervention, an appropriate post on 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 solutions to 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 wiki page or resource. Finally, 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 in 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.xz
Install a 'remote' package (not from a repository):
# pacman -U http://www.example.com/repo/example.pkg.tar.xz
Clean the package cache of packages that are not currently installed (Template:Filename):
# pacman -Sc
Clean the entire package cache:
# pacman -Scc
To remove all the orphan packages:
# pacman -Rns `pacman -Qdtq`