Official Repositories

From ArchWiki

Jump to: navigation, search
i18n
English
Türkçe
Česky
Español
Italiano
简体中文
Português
Nederlands
Français

As there is much confusion about the official repositories, this article attempts to explain their meaning.

Contents

Historical background

Most of the repository splits are for historical reasons. Originally, when Arch Linux was used by very few users, there was only one repository known as [official] (now [core]). At the time, [official] basically contained Judd Vinet's preferred applications. It was designed to contain one of each "type" of program -- one DE, one major browser, etc.

There were users back then that didn't like Judd's selection, so since the Arch Build System is so easy to use, they created packages of their own. These packages went into a repository called [unofficial], and were maintained by developers other than Judd. Eventually, the two repositories were both considered equally supported by the developers, so the names [official] and [unofficial] no longer reflected their true purpose. They were subsequently renamed to [current] and [extra] sometime near the release version 0.5.

Shortly after the 2007.8.1 release, [current] was renamed [core] in order to prevent confusion over what exactly it contains. The repositories are now more or less equal in the eyes of the developers and the community, but [core] does have some differences. The main distinction is that packages used for Installation CDs and release snapshots are taken only from [core]. This repository still gives a complete Linux system, though it may not be the Linux system you want.

Now, sometime around 0.5 or 0.6, they found there were a lot of packages that the developers didn't want to maintain. One of the developers (Xentac) set up the "Trusted User Repositories", which were unofficial repositories in which trusted users could place packages they had created. There was a [staging] repository where packages could be promoted into the official repositories by one of the Arch Linux developers, but other than this, the developers and trusted users were more or less distinct.

This worked for a while, but not when trusted users got bored with their repositories, and not when untrusted users wanted to share their own packages. This led to the development of the AUR. The TUs were conglomerated into a more closely knit group, and they now collectively maintain the [community] repository. The Trusted Users are still a separate group from the Arch Linux developers, and there isn't a lot of communication between them. However, popular packages are still promoted from [community] to [extra] on occasion. The AUR also supports allowing untrusted users to submit PKGBUILDs for other users to use if they wish. These packages are unsupported, and the packages are sometimes called the [unsupported] repository, though since no binary packages are distributed, unsupported isn't really a repository. Trusted users can adopt packages from unsupported into [community] at their discretion, whether it is because the package is popular or because they are interested in maintaining it.

List of repositories

[core]

The [core] repository can be found in core/os/i686 or core/os/x86_64 on your favorite mirror. It contains Arch core packages and some additional software, and will provide you with a fully functional base system.

The installation cd simply contains an installer script, and a snapshot of the core repository.

[extra]

The [extra] repository can be found in extra/os/i686 or extra/os/x86_64 on your favorite mirror. It contains all packages that don't fit in [core]
Example: X.org, window managers, web servers, media players, languages like Python, Ruby and Perl, and a lot more.

[community]

The [community] repository can be found in community/os/i686 or community/os/x86_64 on your favorite mirror. It is maintained by the Trusted Users (TUs) and is part of the Arch User Repository (AUR). It contains packages from the AUR that have enough votes and were adopted by a TU.

[testing]

The [testing] repository can be found in testing/os/i686 on your favorite mirror. [testing] is special because it contains packages that are candidates for the [core] or [extra] repositories. New packages go into [testing] if:

  • they are expected to break something on update and need to be tested first
  • they require other packages to be rebuilt. In this case, all packages that need to be rebuilt are put into [testing] first and when all rebuilds are done, they are moved back to the other repositories.

[testing] is the only repository that can have name collisions with any of the other official repositories. If enabled, it has to be the first repo listed in your pacman.conf file.

Be careful when enabling [testing]. Your system may break after you perform an update with the [testing] repository enabled. Only experienced users who know how to deal with potential system breakage should use it.

[community-testing]

The [community-testing] repository is like the [testing] repository but for packages that are candidates for the [community] repository.

AUR a.k.a. [unsupported]

AUR or Arch User Repository is not really a repository at all. It refers to a database of user-submitted build scripts known as PKGBUILD files, thus this repository truly is unofficial. Users cannot download or install packages from AUR using pacman. They must download the PKGBUILD files and run makepkg which downloads the sources and builds packages. These locally build packages can then be installed using pacman. To automate this task, one of the popular AUR Helpers can be used.

Personal tools