Since only a small part of Arch official packages are nonfree or contain nonfree components, there's no need for us to repackage everything. In our repos, you'll find Arch official packages, directly from its official repositories, minus the nonfree packages, plus our libre replacements, when possible.
- 1 Our current Repos:
1 Our current Repos:
A blue background indicates that the repository is imported from Arch (and run through the blacklist, of course). A purple background indicates that the repository originates with Parabola. A red background indicates that the repository doesn't currently exist in Parabola.
What "-testing" means should be obvious.
The core/extra/libre/java arrangement is a little tricky right now.
First, java. While Java packages in Arch might not have freedom issues per se, they frequently don't meet Parabola's policies with regard to building the package from source. The java repository is a "half way house" for packages that we are fixing this for. In order to not cripple the Java support in Parabola, we must relax the polices in some cases, and provide packages that don't meet all of the criteria to put a package in libre. Packages in java may change quickly.
The libre repository contains four things
- Replacements for packages in Arch's core that were blacklisted (if the replacement isn't in java)
- Replacements for packages in Arch's extra that were blacklisted (if the replacement isn't in java)
- Replacements for packages in Arch's community that were blacklisted (if the replacement isn't in java)
- Packages produced entirely by Parabola that are deemed to be core packages (and their build dependencies)
libre has strict requirements, but currently the sign-off process, where multiple developers vet a package, doesn't reflect this; instead developers are expected to self-review their packages.
In the case of packages being added that aren't replacements for packages from Arch, what belongs in libre is just slightly looser than core, extra and community.
core and extra are imported from Arch, but with blacklisted packages removed.
In Arch, core contains all necessary packages for:
- booting Arch
- connecting to the Internet
- building packages
- management and repair of supported file systems
- the system setup process (e.g. openssh)
as well as dependencies of the above (not necessarily makedepends)
core has fairly strict quality requirements. Multiple developers/users need to signoff on updates before package updates are accepted. For packages with low usage, a reasonable exposure is enough: informing people about update, requesting signoffs, keeping in testing up to a week depending on the severity of the change, lack of outstanding bug reports, along with the implicit signoff of the package maintainer.
In Arch, extra contains all packages that do not fit in core. Example: Xorg, window managers, web browsers, media players, tools for working with languages such as Python and Ruby, and a lot more.
1.2 Community repositories
multilib and libre-multilib contain i686 software and libraries packaged for x86_64 to allow some 32-bit applications to be run on 64-bit systems (such as wine).
community contains packages from the AUR which gained enough votes to be adopted by an Arch "Trusted User".
The Parabola Community Repository, or pcr contains packages maintained by trusted members of the Parabola community. It also contains packages maintained by Parabola developers, but that the developer decided didn't belong in core/libre.
nonprism contains packages provided by the Parabola community without services under global data surveillance programs like PRISM.
cross contains mostly-unsupported packages that contain toolchains for cross-compiling for a different architecture.
1.3 Unsupported repositories
unmaintained contains detected unsecured (long time) unmaintained packages. It means packages without updates with security vulnerabilities known.
1.3.2 User repositories
Repositories beginning with a tilde (~) are "user" repositories, and they are provided by individual developers independent of the Parabola project. The individual might be a Parabola developer, but their repository is only supported by them, not the rest of the Parabola team.
That said, the packages in them must still meet the freedom requirements of Parabola. However, they might not meet the quality or stability requirements.
In general, user repositories are being phased out in favor of pcr. However, they aren't going away, or being totally deprecated. For example, ~lukeshu is going to continue to be used for testing/unstable software that is developed by Luke Shumaker, but is not part of Parabola.
Parabola does not endorse the AUR (Arch User Repository). Often users switching from Arch ask if the AUR is supported in Parabola. Our answer is "no, but it isn't in Arch either." However, it is at least partially endorsed by Arch.
Packages and scripts there are untrusted, and the burden is on the user to inspect the PKGBUILD and resulting package. This is the same in Parabola and Arch. Any packages that you build yourself are, naturally, your responsibility, not Parabola's. Many (most?) of the packages there are of poor quality, and contain incorrect information regarding licenses.
If there is a package in AUR that you would like, you are encouraged to ask one of the Parabola contributors to pick it up and add it to pcr.