![]() ![]() While it is unlikely that you will need to modify the default nf for most installations, you can change default installation and logging directories and specify packages to be held back from upgrades. You may access the manual page for this configuration file with the command man nf. The options in the stock /etc/nf are documented in comments, and are beyond the scope of this document. The mirror list was created and prioritized during the installation process and you probably will not need to alter this. The configuration for pacman is defined in the /etc/nf file, while the addresses of the repository mirrors are contained in /etc/pacman.d/mirrorlist. Removes packages that are unneeded by any other packages. This command is the inverse of pacman -S. Removes a package and its dependencies, as long as the dependencies are not needed and were not explicitly installed by the user. Ignores upgrades to a given package or list of packages. Removes uninstalled packages from the cache and attempts to clean up old copies of the repository database. The update and refresh command can (and should) be run together, as in: pacman -Syu. Triggers a full system update and downloads new packages to upgrade the system. Triggers a database refresh, and synchronizes the local database with the remote database. Lists out-of-date installed packages that are in need of an update. Searches among the installed packages for a given package. Outputs the version number and name of the package that “owns” a given file. Here are some examples with brief descriptions:ĭisplays information about a given package, including dependency information, the date of the package, a link to the upstream source and other useful information. They are often combined with additional flags (also case-sensitive) to alter the functionality of the command. Removes the specified package or packages.Įach of the above single character flags ( -Q, -S, and -R) are uppercase. Installs new packages, downloads new content for the database and/or upgrades the system, depending on the options and the named package or packages. Searches the package database for a package name (and optional version number). There are three core commands for basic package management: While the pacman tool is very powerful, it’s also quite simple. If you’re not familiar with the sudo command, see the Linux Users and Groups guide. If you are logged in as the root use (not recommended), you can omit the sudo prefix if desired. Some commands in this guide require elevated privileges and are prefixed with the sudo command. Review the Setting Up and Securing a Compute Instance guide for assistance on creating and securing a standard user account. Login credentials to the system for either the root user (not recommended) or a standard user account (belonging to the sudo group) and the ability to access the system through SSH or Lish. Review the Creating a Compute Instance guide if you do not yet have a compatible system. Before You Beginīefore running the commands within this guide, you will need:Ī system running Arch Linux or an Arch-based distribution like Manjaro. Therefore, administrators of Arch Linux must consider the output of pacman carefully before agreeing to upgrade or update any packages. This means that there aren’t release versions of Arch, as all systems, once upgraded, are equivalent. ![]() Arch Linux runs on a rolling release schedule, which means packages are added to the main repository when they (and their dependencies) are ready for production. tar.xz format, and also provides a “ports” build system that facilitates building packages. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |