Professional Documents
Culture Documents
org/title/Pacman/Tips_and_tricks#aria2
For general methods to improve the flexibility of the provided tips or Related articles
pacman itself, see Core utilities and Bash.
Mirrors
Creating packages
Contents
Maintenance
Listing packages
With version
With size
Individual packages
Packages and dependencies
By date
Not in a specified group, repository or meta package
Development packages
Browsing packages
Listing files owned by a package with size
Identify files not owned by any package
Tracking unowned files created by packages
Removing unused packages (orphans)
Removing everything but essential packages
Getting the dependencies list of several packages
Listing changed backup files
Back up the pacman database
Check changelogs easily
Installation and recovery
Installing packages from a CD/DVD or USB stick
Custom local repository
Network shared pacman cache
Read-only cache
Overlay mount of read-only cache
Distributed read-only cache
Read-write cache
two-way with rsync
Dynamic reverse proxy cache using nginx
1 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
Maintenance
Note: Instead of using comm (which requires sorted input with sort) in the sections below, you may
also use grep -Fxf or grep -Fxvf .
Listing packages
With version
You may want to get the list of installed packages with their version, which is useful when reporting
bugs or discussing installed packages.
2 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
With size
Figuring out which packages are largest can be useful when trying to free space on your hard drive.
There are two options here: get the size of individual packages, or get the size of packages and their
dependencies.
Individual packages
The following command will list all installed packages and their individual sizes:
$ LC_ALL=C pacman -Qi | awk '/^Name/{name=$3} /^Installed Size/{print $4$5, name}' | sort -h
To list the download size of several packages (leave packages blank to list all packages):
To list explicitly installed packages not in the meta package base (https://archlinux.org/
packages/?name=base) nor package group base-devel (https://archlinux.org/gr
oups/x86_64/base-devel/) with size and description:
$ expac -H M "%011m\t%-20n\t%10d" $(comm -23 <(pacman -Qqen | sort) <({ pacman -Qqg base-devel; expac -l '\n
' '%E' base; } | sort | uniq)) | sort -n
To list the packages marked for upgrade with their download size
3 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
By date
Note: To get a list of packages installed as dependencies but no longer required by any installed
package, see #Removing unused packages (orphans).
$ comm -23 <(pacman -Qqe | sort) <(expac -l '\n' '%E' base | sort)
$ comm -23 <(pacman -Qqe | sort) <({ pacman -Qqg base-devel; expac -l '\n' '%E' base; } | sort -u)
List all installed packages unrequired by other packages, and which are not in the base (https://
archlinux.org/packages/?name=base) meta package or base-devel (https://archli
nux.org/groups/x86_64/base-devel/) package group:
$ comm -23 <(pacman -Qqt | sort) <({ pacman -Qqg base-devel; expac -l '\n' '%E' base; } | sort -u)
$ expac -H M '%-20n\t%10d' $(comm -23 <(pacman -Qqt | sort) <({ pacman -Qqg base-devel; expac -l '\n' '%E' b
ase; } | sort -u))
List all installed packages that are not in the specified repository repo_name
4 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
List all packages on the Arch Linux ISO that are not in the base (https://archlinux.org/pac
kages/?name=base) meta package:
Tip: Alternatively, use combine (instead of comm ) from the moreutils (https://archlinux.org/packag
es/?name=moreutils) package which has a syntax that is easier to remember. See combine(1) (http
s://man.archlinux.org/man/combine.1).
Development packages
Browsing packages
$ pacman -Qq | fzf --preview 'pacman -Qil {}' --layout=reverse --bind 'enter:execute(pacman -Qil {} | less)'
This uses fzf to present a two-pane view listing all packages with package info shown on the right.
Enter letters to filter the list of packages; use arrow keys (or Ctrl-j / Ctrl-k ) to navigate; press
Enter to see package info under less.
To browse all packages currently known to pacman (both installed and not yet installed) in a similar
way, using fzf, use:
The navigational keybindings are the same, although Enter will not work in the same way.
This one might come in handy if you have found that a specific package uses a huge amount of space
and you want to find out which files make up the most of that.
If your system has stray files not owned by any package (a common case if you do not use the
5 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
package manager to install software), you may want to find such files in order to clean them up.
One method is to use pacreport --unowned-files as the root user from pacutils (http
s://archlinux.org/packages/?name=pacutils) which will list unowned files among other
details.
Another is to list all files of interest and check them against pacman:
# find /etc /usr /opt | LC_ALL=C pacman -Qqo - 2>&1 >&- >/dev/null | cut -d ' ' -f 5-
/etc/pacreport.conf
[Options]
IgnoreUnowned = usr/share/applications/mimeinfo.cache
[PkgIgnoreUnowned]
alsa-utils = var/lib/alsa/asound.state
bluez = var/lib/bluetooth
ca-certificates = etc/ca-certificates/trust-source/*
dbus = var/lib/dbus/machine-id
glibc = etc/ld.so.cache
grub = boot/grub/*
linux = boot/initramfs-linux.img
pacman = var/lib/pacman/local
update-mime-database = usr/share/mime/magic
Then, when using pacreport --unowned-files as the root user, any unowned files will be listed
if the associated package is no longer installed (or if any new files have been created).
6 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
Note: The arguments -Qt list only true orphans. To include packages which are optionally required
by another package, pass the -t flag twice (i.e., -Qtt ).
If it is ever necessary to remove all packages except the essentials packages, one method is to set the
installation reason of the non-essential ones as dependency and then remove all unnecessary
dependencies.
First, for all the packages installed "as explicitly", change their installation reason to "as dependency":
Then, change the installation reason to "as explicitly" of only the essential packages, those you do not
want to remove, in order to avoid targeting them:
Note:
▪ Additional packages can be added to the above command in order to avoid being removed.
See Installation guide#Install essential packages for more info on other packages that may
be necessary for a fully functional base system.
▪ This will also select the bootloader's package for removal. The system should still be bootable,
but the boot parameters might not be changeable without it.
Finally, follow the instructions in #Removing unused packages (orphans) to remove all
packages that have installation reason "as dependency".
Note: To only show the tree of local installed packages, use pacman -Qi .
$ LC_ALL=C pacman -Si packages | awk -F'[:<=>]' '/^Depends/ {print $2}' | xargs -n1 | sort -u
7 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
If you want to back up your system configuration files, you could copy all files in /etc/ but usually
you are only interested in the files that you have changed. Modified backup files can be viewed with
the following command:
Running this command with root permissions will ensure that files readable only by root (such as
/etc/sudoers ) are included in the output.
Tip: See #Listing all changed files from packages to list all changed files pacman knows
about, not only backup files.
The following command can be used to back up the local pacman database:
Store the backup pacman database file on one or more offline media, such as a USB stick, external
hard drive, or CD-R.
The database can be restored by moving the pacman_database.tar.bz2 file into the / directory
and executing the following command:
Note: If the pacman database files are corrupted, and there is no backup file available, there exists
some hope of rebuilding the pacman database. Consult #Restore pacman's local database.
When maintainers update packages, commits are often commented in a useful fashion. Users can
quickly check these from the command line by installing pacolog (https://aur.archlinux.o
rg/packages/pacolog/)AUR. This utility lists recent commit messages for packages from the
official repositories or the AUR, by using pacolog <package> .
8 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
# cd ~/Packages
# pacman -Syw --cachedir . base base-devel grub-bios xorg gimp
# repo-add ./custom.db.tar.gz ./*
Pacman, which will reference the host installation by default, will not properly resolve and download
existing dependencies. In cases where all packages and dependencies are wanted, it is recommended
to create a temporary blank DB and reference it with --dbpath :
# mkdir /tmp/blankdb
# pacman -Syw --cachedir . --dbpath /tmp/blankdb base base-devel grub-bios xorg gimp
# repo-add ./custom.db.tar.gz ./*
Then you can burn the "Packages" folder to a CD/DVD or transfer it to a USB stick, external HDD, etc.
To install:
# mkdir /mnt/repo
# mount /dev/sr0 /mnt/repo #For a CD/DVD.
# mount /dev/sdxY /mnt/repo #For a USB stick.
2. Edit pacman.conf and add this repository before the other ones (e.g. extra, core, etc.). This is
important. Do not just uncomment the one on the bottom. This way it ensures that the files from the
CD/DVD/USB take precedence over those in the standard repositories:
/etc/pacman.conf
[custom]
SigLevel = PackageRequired
Server = file:///mnt/repo/Packages
3. Finally, synchronize the pacman database to be able to use the new repository:
# pacman -Syu
Use the repo-add script included with pacman to generate a database for a personal repository. Use
repo-add --help for more details on its usage. A package database is a tar file, optionally
9 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
compressed. Valid extensions are .db or .files followed by an archive extension of .tar, .tar.gz,
.tar.bz2, .tar.xz, .tar.zst, or .tar.Z. The file does not need to exist, but all parent directories must exist.
To add a new package to the database, or to replace the old version of an existing package in the
database, run:
The database and the packages do not need to be in the same directory when using repo-add, but
keep in mind that when using pacman with that database, they should be together. Storing all the
built packages to be included in the repository in one directory also allows to use shell glob expansion
to add or update multiple packages at once:
Warning: repo-add adds the entries into the database in the same order as passed on the
command line. If multiple versions of the same package are involved, care must be taken to ensure
that the correct version is added last. In particular, note that lexical order used by the shell depends
on the locale and differs from the vercmp(8) (https://man.archlinux.org/man/vercmp.8) ordering
used by pacman.
If you are looking to support multiple architectures then precautions should be taken to prevent
errors from occurring. Each architecture should have its own directory tree:
/home/archie/customrepo/
└── <arch>
├── customrepo.db -> customrepo.db.tar.xz
├── customrepo.db.tar.xz
├── customrepo.files -> customrepo.files.tar.xz
├── customrepo.files.tar.xz
└── personal-website-git-b99cce0-1-<arch>.pkg.tar.xz
1 directory, 5 files
The repo-add executable checks if the package is appropriate. If this is not the case you will be
running into error messages similar to this:
==> ERROR: '/home/archie/customrepo/<arch>/foo-<arch>.pkg.tar.xz' does not have a valid database archive ext
ension.
repo-remove is used to remove packages from the package database, except that only package names
are specified on the command line.
Once the local repository database has been created, add the repository to pacman.conf for each
system that is to use the repository. An example of a custom repository is in pacman.conf . The
repository's name is the database filename with the file extension omitted. In the case of the example
10 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
above the repository's name would simply be repo. Reference the repository's location using a
file:// url, or via FTP using ftp://localhost/path/to/directory.
If willing, add the custom repository to the list of unofficial user repositories, so that the
community can benefit from it.
If you happen to run several Arch boxes on your LAN, you can share packages so that you can greatly
decrease your download times. Keep in mind you should not share between different architectures
(i.e. i686 and x86_64) or you will run into problems.
Read-only cache
Note: If pacman fails to download 3 packages from the server, it will use another mirror instead.
See https://bbs.archlinux.org/viewtopic.php?id=268066.
If you are looking for a quick solution, you can simply run a standalone webserver, e.g. darkhttpd
(https://archlinux.org/packages/?name=darkhttpd), which other computers can use
as a first mirror:
# ln -s /var/lib/pacman/sync/*.db /var/cache/pacman/pkg
$ sudo -u http darkhttpd /var/cache/pacman/pkg --no-server-id
You could also run darkhttpd as a systemd service for convenience. Just add this server at the top of
your /etc/pacman.d/mirrorlist in client machines with
Server = http://mymirror:8080 . Make sure to keep your mirror updated.
If you are already running a web server for some other purpose, you might wish to reuse that as your
local repository server instead of darkhttpd. For example, if you already serve a site with nginx, you
can add an nginx server block listening on port 8080:
/etc/nginx/nginx.conf
server {
listen 8080;
root /var/cache/pacman/pkg;
server_name myarchrepo.localdomain;
try_files $uri $uri/;
}
Whichever web server you use, remember to open port 8080 to local traffic (and you probably want to
deny anything not local). For example, if using iptables, add
-s 192.168.0.0/16 -p tcp --dport 8080 -j ACCEPT to your ruleset (adjust for your LAN
subnet if necessary).
11 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
It is possible to use one machine on a local network as a read-only package cache by overlay
mounting its /var/cache/pacman/pkg directory. Such a configuration is advantageous if this
server has installed on it a reasonably comprehensive selection of up-to-date packages which are also
used by other boxes. This is useful for maintaining a number of machines at the end of a low
bandwidth upstream connection.
Note concerning overlay: The working directory must be an empty directory on the same
mounted device as the upper directory.
After this, run pacman using the option --cachedir /tmp/pacman_pkg , e.g.:
There are Arch-specific tools for automatically discovering other computers on your network offering
a package cache. Try pacredir (https://archlinux.org/packages/?name=pacredir),
pacserve, pkgdistcache (https://aur.archlinux.org/packages/pkgdistcache/)
AUR, or paclan (https://aur.archlinux.org/packages/paclan/)AUR. pkgdistcache uses
Avahi instead of plain UDP which may work better in certain home networks that route instead of
bridge between WiFi and Ethernet.
Read-write cache
In order to share packages between multiple computers, simply share /var/cache/pacman/ using
any network-based mount protocol. This section shows how to use shfs or SSHFS to share a package
cache plus the related library-directories between multiple computers on the same local network.
Keep in mind that a network shared cache can be slow depending on the file-system choice, among
other factors.
Tip:
▪ To use sshfs or shfs, consider reading Using SSH Keys.
12 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
▪ By default, smbfs does not serve filenames that contain colons, which results in the client
downloading the offending package afresh. To prevent this, use the mapchars mount option
on the client.
Then, to share the actual packages, mount /var/cache/pacman/pkg from the server to
/var/cache/pacman/pkg on every client machine.
Warning: Do not make /var/cache/pacman/pkg or any of its ancestors (e.g., /var ) a symlink.
Pacman expects these to be directories. When pacman re-installs or upgrades itself, it will remove
the symlinks and create empty directories instead. However during the transaction pacman relies
on some files residing there, hence breaking the update process. Refer to FS#50298 (https://bug
s.archlinux.org/task/50298) for further details.
Another approach in a local environment is rsync. Choose a server for caching and enable the
Rsync#rsync daemon. On clients synchronize two-way with this share via the rsync protocol.
Filenames that contain colons are no problem for the rsync protocol.
Draft example for a client, using uname -m within the share name ensures an architecture-
dependent sync:
nginx can be used to proxy package requests to official upstream mirrors and cache the results to the
local disk. All subsequent requests for that package will be served directly from the local cache,
minimizing the amount of internet traffic needed to update a large number of computers.
In this example, the cache server will run at http://cache.domain.example:8080/ and store
the packages in /srv/http/pacman-cache/ .
Install nginx on the computer that is going to host the cache. Create the directory for the cache and
adjust the permissions so nginx can write files to it:
# mkdir /srv/http/pacman-cache
# chown http:http /srv/http/pacman-cache
13 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
In order to use the cache each Arch Linux computer (including the one hosting the cache) must have
the following line at the top of the mirrorlist file:
/etc/pacman.d/mirrorlist
Server = http://cache.domain.example:8080/$repo/os/$arch
...
Note: You will need to create a method to clear old packages, as the cache directory will continue to
grow over time. paccache (which is provided by pacman-contrib (https://archlinux.org/packages/?n
ame=pacman-contrib)) can be used to automate this using retention criteria of your choosing. For
example, find /srv/http/pacman-cache/ -type d -exec paccache -v -r -k 2 -c {} \; will keep the last
2 versions of packages in your cache directory.
/etc/pacoloco.yaml
port: 9129
repos:
mycopy:
urls:
- http://mirror.lty.me/archlinux
- http://mirrors.kernel.org/archlinux
Use Syncthing or Resilio Sync to synchronize the pacman cache folders (i.e.
/var/cache/pacman/pkg ).
14 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
By default, pacman -Sc removes package tarballs from the cache that correspond to packages that
are not installed on the machine the command was issued on. Because pacman cannot predict what
packages are installed on all machines that share the cache, it will end up deleting files that should not
be.
To clean up the cache so that only outdated tarballs are deleted, add this entry in the [options]
section of /etc/pacman.conf :
CleanMethod = KeepCurrent
Keeping a list of all the explicitly installed packages can be useful, to backup a system for example or
speed up installation on a new system:
Note:
▪ With option -t , the packages already required by other explicitly installed packages are not
mentioned. If reinstalling from this list they will be installed but as dependencies only.
▪ With option -n , foreign packages (e.g. from AUR) would be omitted from the list.
▪ Use
comm -13 <(pacman -Qqdt | sort) <(pacman -Qqdtt | sort) >
optdeplist.txt
to also create a list of the installed optional dependencies which can be reinstalled with
--asdeps .
▪ Use pacman -Qqem > foreignpkglist.txt to create the list of AUR and other foreign
packages that have been explicitly installed.
To keep an up-to-date list of explicitly installed packages (e.g. in combination with a versioned
/etc/ ), you can set up a hook. Example:
[Trigger]
Operation = Install
Operation = Remove
Type = Package
Target = *
15 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
[Action]
When = PostTransaction
Exec = /bin/sh -c '/usr/bin/pacman -Qqe > /etc/pkglist.txt'
To install packages from a previously saved list of packages, while not reinstalling previously installed
packages that are already up-to-date, run:
However, it is likely foreign packages such as from the AUR or installed locally are present in the list.
To filter out from the list the foreign packages, the previous command line can be enriched as follows:
Eventually, to make sure the installed packages of your system match the list and remove all the
packages that are not mentioned in it:
If you are suspecting file corruption (e.g. by software/hardware failure), but are unsure if files were
corrupted, you might want to compare with the hash sums in the packages. This can be done with
pacutils (https://archlinux.org/packages/?name=pacutils):
For recovery of the database see #Restore pacman's local database. The mtree files can also be
extracted as .MTREE from the respective package files.
Note: This should not be used as is when suspecting malicious changes! In this case security
precautions such as using a live medium and an independent source for the hash sums are advised.
16 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
Foreign (AUR) packages must be reinstalled separately; you can list them with pacman -Qqm .
Warning: To force all packages to be overwritten, use --overwrite=* , though this should be an
absolute last resort. See System maintenance#Avoid certain pacman commands.
If you have Arch installed on a USB key and manage to mess it up (e.g. removing it while it is still
being written to), then it is possible to re-install all the packages and hopefully get it back up and
working again (assuming USB key is mounted in /newarch )
For example, if you want to see the contents of /etc/systemd/logind.conf supplied within the
systemd (https://archlinux.org/packages/?name=systemd) package:
$ vim /var/cache/pacman/pkg/systemd-204-3-x86_64.pkg.tar.xz
Already running processes do not automatically notice changes caused by updates. Instead, they
continue using old library versions. That may be undesirable, due to potential issues related to
security vulnerabilities or other bugs, and version incompatibility.
Processes depending on updated libraries may be found using either htop (https://archlinu
x.org/packages/?name=htop), which highlights the names of the affected programs, or with a
snippet based on lsof (https://archlinux.org/packages/?name=lsof), which also
prints the names of the libraries:
# lsof +c 0 | grep -w DEL | awk '1 { print $1 ": " $NF }' | sort -u
17 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
This solution will only detect files, that are normally kept opened by running processes, which
basically limits it to shared libraries ( .so files). It may miss some dependencies, like those of Java or
Python applications.
Many packages attempt to install documentation and translations in several languages. Some
programs are designed to remove such unnecessary files, such as localepurge (https://aur.a
rchlinux.org/packages/localepurge/)AUR, which runs after a package is installed to delete
the unneeded locale files. A more direct approach is provided through the NoExtract directive in
pacman.conf , which prevent these files from ever being installed.
Warning: Some users noted that removing locales has resulted in unintended consequences,
even under Xorg (https://bbs.archlinux.org/viewtopic.php?id=250846).
/etc/pacman.conf
Performance
Download speeds
When downloading packages pacman uses the mirrors in the order they are in
/etc/pacman.d/mirrorlist . The mirror which is at the top of the list by default however may
not be the fastest for you. To select a faster mirror, see Mirrors.
Pacman's speed in downloading packages can also be improved by using a different application to
download packages, instead of pacman's built-in file downloader, or by enabling parallel
downloads.
In all cases, make sure you have the latest pacman before doing any modifications.
18 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
# pacman -Syu
Powerpill
Powerpill is a pacman wrapper that uses parallel and segmented downloading to try to speed up
downloads for pacman.
wget
This is also very handy if you need more powerful proxy settings than pacman's built-in capabilities.
Instead of uncommenting the wget parameters in /etc/pacman.conf , you can also modify the
wget configuration file directly (the system-wide file is /etc/wgetrc , per user files are
$HOME/.wgetrc ).
aria2
aria2 is a lightweight download utility with support for resumable and segmented HTTP/HTTPS and
FTP downloads. aria2 allows for multiple and simultaneous HTTP/HTTPS and FTP connections to an
Arch mirror, which should result in an increase in download speeds for both file and package
retrieval.
Note: Using aria2c in pacman's XferCommand will not result in parallel downloads of multiple
packages. Pacman invokes the XferCommand with a single package at a time and waits for it to
complete before invoking the next. To download multiple packages in parallel, see Powerpill.
Tip: This alternative configuration for using pacman with aria2 (https://bbs.archlinu
x.org/viewtopic.php?pid=1491879#p1491879) tries to simplify configuration and adds more
configuration options.
19 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
▪ -d, --dir : The directory to store the downloaded file(s) as specified by pacman.
▪ -o, --out : The output file name(s) of the downloaded file(s).
▪ %o : Variable which represents the local filename(s) as specified by pacman.
▪ %u : Variable which represents the download URL as specified by pacman.
Other applications
There are other downloading applications that you can use with pacman. Here they are, and their
associated XferCommand settings:
Utilities
▪ Lostfiles — Script that identifies files not owned by any package.
▪ Pacmatic — Pacman wrapper to check Arch News before upgrading, avoid partial upgrades, and
warn about configuration file changes.
▪ pkgtop — Interactive package manager and resource monitor designed for the GNU/Linux.
20 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
▪ Powerpill — Uses parallel and segmented downloading through aria2 and Reflector to try to
speed up downloads for pacman.
▪ snap-pac — Make pacman automatically use snapper to create pre/post snapshots like
openSUSE's YaST.
▪ vrms-arch — A virtual Richard M. Stallman to tell you which non-free packages are installed.
Graphical
Warning: PackageKit opens up system permissions by default, and is otherwise not recommended
for general usage. See FS#50459 (https://bugs.archlinux.org/task/50459) and FS#57943
(https://bugs.archlinux.org/task/57943).
▪ Apper — Qt 5 application and package manager using PackageKit written in C++. Supports
AppStream metadata (https://www.freedesktop.org/wiki/Distributions/AppStream/).
▪ Deepin App Store — Third party app store for DDE built with DTK, using PackageKit. Supports
AppStream metadata (https://www.freedesktop.org/wiki/Distributions/AppStream/).
21 of 22 12/6/21, 03:01
pacman/Tips and tricks - ArchWiki https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#aria2
Content is available under GNU Free Documentation License 1.3 or later unless otherwise noted.
22 of 22 12/6/21, 03:01