{"id":4375,"date":"2023-06-12T10:25:15","date_gmt":"2023-06-12T17:25:15","guid":{"rendered":"https:\/\/jasonsblog.ddns.net\/?p=4375"},"modified":"2023-06-12T11:47:03","modified_gmt":"2023-06-12T18:47:03","slug":"the-beginners-guide-to-using-pacman-on-arch-linux","status":"publish","type":"post","link":"https:\/\/jasonsblog.ddns.net\/index.php\/2023\/06\/12\/the-beginners-guide-to-using-pacman-on-arch-linux\/","title":{"rendered":"The Beginner’s Guide to Using Pacman on Arch Linux"},"content":{"rendered":"\n

This is a good write up on using Pacman with some options you wouldn’t use that often, so if you’re newer to Arch or Arch based distributions like I am, this is a good overview and reference to build upon. For example, I like to use “sudo pacman -Syyuu” when I update. But of particular interest removing packages with dependencies no longer in use, removing orphaned packages, and clearing the package cache which could be taking up gigabytes of disk space.<\/p>\n\n\n\n

https:\/\/linuxiac.com\/how-to-use-pacman-to-manage-software-on-arch-linux\/<\/a><\/p>\n\n\n

<\/div><\/div><\/div>\n\n\n

By Bobby Borisov<\/p>\n\n\n\n

This guide shows how to use Pacman package manager on Arch Linux to manage the software by installing, removing, and updating packages.<\/strong><\/p>\n\n\n\n

Want to install packages on Arch Linux but need to know how? Many people run into this issue when they first move to Arch<\/a>. But don\u2019t worry; you can easily manage packages on your Arch system using the pacman<\/code> command. But first, let\u2019s answer an important question.<\/p>\n\n\n\n

What Is Pacman Package Manager?<\/h2>\n\n\n\n

Pacman (stands for Pac<\/strong>kage Man<\/strong>ager) is the default package manager for Arch Linux<\/a>, a lightweight and flexible distro popular among experienced Linux users. Like Arch, Pacman is known for its simplicity, speed, and reliability, combining a simple binary package format with an easy-to-use build system.<\/p>\n\n\n\n

Pacman keeps the system up to date by synchronizing package lists with the official Arch repositories. In addition, this client-server model allows the user to download\/install packages with a simple command, complete with all required dependencies.<\/p>\n\n\n\n

What Will You Learn in This Guide?<\/h2>\n\n\n\n

We will cover the basics of Pacman, including how to install, update, and remove packages, as well as some more advanced features and tips for using Pacman to its full potential. So, whether you are new to Arch or an experienced Linux user, this guide will help you get the most out of the Pacman.<\/p>\n\n\n\n

In addition, this guide also applies to all Arch-based Linux distros<\/a>, such as Manjaro, EndeavourOS, Garuda Linux, etc., using Pacman as the package manager.<\/p>\n\n\n\n

Of course, the official packages are just one of the sources of software on Arch. In addition, you can install some of the thousands available in the AUR repository \u2013 Arch\u2019s most significant asset that differentiates it from all other Linux distributions.<\/p>\n\n\n\n

However, to do this, different Pacman tools are used, known as AUR helpers. In that case, our comprehensive guide on the subject, \u201cHow to Install AUR Packages in Arch Linux<\/a>,\u201d will greatly help you.<\/p>\n\n\n\n

Finally, you can even use one of the excellent GUI Pacman frontends<\/a> to make installing packages in Arch as easy as possible.<\/p>\n\n\n\n

Refresh Package Lists<\/h2>\n\n\n\n

Because Arch is a rolling-release distro<\/a>, new packages are added to the distro\u2019s repositories as soon as they are released. As a result, you should keep the Pacman database up to date by updating it fairly frequently.<\/p>\n\n\n\n

So, to update the package lists before installing any packages or updating the system, perform the following:<\/p>\n\n\n\n

sudo pacman -Sy<\/code><\/pre>\n\n\n\n
Searching for Package<\/h2>\n\n\n\n
To search for a specific package, for example, vlc<\/code>, from a sync database (remote server), run:<\/p>\n\n\n\n
sudo pacman -Ss vlc<\/code><\/pre>\n\n\n\n
This returns all packages with a matching \u201cvlc<\/em>\u201d string in the package name or description.<\/p>\n\n\n\n
Getting Information About Package<\/h2>\n\n\n\n
To display the detailed information of the given package from the sync database, for example, nginx<\/code>, run:<\/p>\n\n\n\n
pacman -Si nginx<\/code><\/pre>\n\n\n\n
Installing a New Package with Pacman<\/h2>\n\n\n\n
Installing a package with Pacman is easy. Just run the following command:<\/p>\n\n\n\n
sudo pacman -S vlc<\/code><\/pre>\n\n\n\n
As a result, this process will automatically identify all the necessary dependencies and take care of them. In addition, to install multiple packages with a single command, use a space-separated list of packages.<\/p>\n\n\n\n
Installing a Local Package<\/h2>\n\n\n\n
Pacman stores all downloaded packages in the \/var\/cache\/pacman\/pkg<\/code> directory.<\/p>\n\n\n\n
In case you want to install the locally downloaded package, for example, vlc<\/code>, located in \/var\/cache\/pacman\/pkg\/ directory, go to the folder where the package is located and enter the following command:<\/p>\n\n\n\n
cd \/var\/cache\/pacman\/pkg\/\nsudo pacman -U vlc-3.0.11-2-x86_64.pkg.tar.zst<\/code><\/pre>\n\n\n\n
Update\/Upgrade a Package<\/h2>\n\n\n\n
To update a single package, for example, rsync<\/code>, run the following:<\/p>\n\n\n\n
sudo pacman -S rsync<\/code><\/pre>\n\n\n\n
To update all packages at once on your system, just run the following:<\/p>\n\n\n\n
sudo pacman -Syu<\/code><\/pre>\n\n\n\n
However, sometimes you want to upgrade the packages, but you want it to stay at an older version (because you know the newer version has removed a feature or is broken).<\/p>\n\n\n\n
So, if the vlc<\/code> package was causing the problem, you could use the following command for this:<\/p>\n\n\n\n
sudo pacman -Syu --ignore=vlc<\/code><\/pre>\n\n\n\n
Remove a Package with Pacman<\/h2>\n\n\n\n
To remove a package alongside with all its dependencies, run the following command:<\/p>\n\n\n\n
sudo pacman -Rs vlc<\/code><\/pre>\n\n\n\n
This command will altogether remove the vlc<\/code> package and all dependencies. While removing packages, Pacman will keep the critical configuration files with the extension .pacsave<\/code>.<\/p>\n\n\n\n
In addition, if you no longer want them and want to free up the hard drive, you can remove the package along with all its configuration files with the command:<\/p>\n\n\n\n
sudo pacman -Rns vlc<\/code><\/pre>\n\n\n\n
Remove Orphaned (Unused) Packages<\/h2>\n\n\n\n
After removing a package in Arch Linux, there may still be some remaining orphaned (unused) packages that were dependencies of the removed package. However, these orphaned packages are not required anymore, so we can get rid of them to free up some space.<\/p>\n\n\n\n
To remove these packages, run:<\/p>\n\n\n\n
sudo pacman -Rns $(pacman -Qdtq)<\/code><\/pre>\n\n\n\n
If no orphans were found, the output is:<\/p>\n\n\n\n
Searching for Already Installed Packages<\/h2>\n\n\n\n
Sometimes you want to check for a specific package if it is installed locally. In this case, you can do it using the command below:<\/p>\n\n\n\n
pacman -Qs vlc<\/code><\/pre>\n\n\n\n
You can view a list of all the packages installed on your system using the following command:<\/p>\n\n\n\n
pacman -Q<\/code><\/pre>\n\n\n\n
Find All Files Owned by a Package<\/h2>\n\n\n\n
You can find all the files that are installed by a specific package using the following command:<\/p>\n\n\n\n
pacman -Ql vlc<\/code><\/pre>\n\n\n\n
This returns the package name and the path to files that it owns.<\/p>\n\n\n\n
Find the Package Owner of the File<\/h2>\n\n\n\n
If you want to check the location of the binary executable file owned by a package, use the -Qo<\/code> flag.<\/p>\n\n\n\n
pacman -Qo \/usr\/bin\/vlc<\/code><\/pre>\n\n\n\n
Download a Package<\/h2>\n\n\n\n
Sometimes, you can download a package and keep it in your cache without installing it. For example, you can use the downloaded package later. To do so, run:<\/p>\n\n\n\n
pacman -Sw vlc<\/code><\/pre>\n\n\n\n
The above command will only download the vlc<\/code> package and keep it in the cache folder. Pacman stores all downloaded packages in the \/var\/cache\/pacman\/pkg<\/code> directory.<\/p>\n\n\n\n
Clean-Up Package Cache<\/h2>\n\n\n\n
All packages we downloaded during the installation will be stored in the cache directory, i.e., \/var\/cache\/pacman\/pkg\/<\/code>. But if you don\u2019t remove them periodically, they will slowly eat up your hard drive space; sooner or later, you could end up with low disk space<\/a>.<\/p>\n\n\n\n
So it is good to remove the cache periodically. For example, to remove all the cached packages and the unused sync database, execute the following:<\/p>\n\n\n\n
sudo pacman -Sc<\/code><\/pre>\n\n\n\n
In addition, if you want to remove all files from the cache, use the clean c<\/code> switch twice. Of course, this is the most aggressive approach and will leave nothing in the cache folder:<\/p>\n\n\n\n
sudo pacman -Scc<\/code><\/pre>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
Arch Linux is one of the most reputed and famous Linux distributions. This guide has covered most of the commands you need to know when using Pacman to install, update, and remove software on Arch.<\/p>\n\n\n\n
I hope that it was helpful in your journey with Arch. The official Arch Linux Wiki<\/a> provides detailed documentation about the Pacman package manager.<\/p>\n","protected":false},"excerpt":{"rendered":"
This is a good write up on using Pacman with some options you wouldn’t use that often, so if you’re newer to Arch or Arch based distributions like I am, this is a good overview and reference to build upon. For example, I like to use “sudo pacman -Syyuu” when I update. But of particular […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-4375","post","type-post","status-publish","format-standard","hentry","category-tech"],"blocksy_meta":[],"featured_image_src":null,"author_info":{"display_name":"Jason","author_link":"https:\/\/jasonsblog.ddns.net\/index.php\/author\/jturning\/"},"_links":{"self":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/4375","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/comments?post=4375"}],"version-history":[{"count":4,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/4375\/revisions"}],"predecessor-version":[{"id":4397,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/4375\/revisions\/4397"}],"wp:attachment":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/media?parent=4375"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/categories?post=4375"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/tags?post=4375"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}