While distributions typically have high quality packages that work fine, a lot of software is not packaged in distributions.
This often lead users to rely on third party package managers that are often provided by the distribution.
This page tries to summarize the research about such third party package managers, especially to understand which one can be added in or kept in FSDG compliant distributions, and which ones should be removed or replaced.
Read a related article: Keeping track of freedom while managing packages
FSDG compliant repositories
This contains lists of FSDG compliant repositories.
|Repository type||FSDG compliant implementations|
|Browser addons||See BrowserAddons|
|Emacs packages repositories|
|General purpose package manager on top of existing distributions|
|Kernel packages repositories|
The CrossDistroBootstrap also has some information on how reusable are some FSDG distribution repositories. For instance PureOS is now in upstream debootstrap, but other FSDG compliant distributions need to wait for a new debootstrap release, and they might also need to package the PureOS keyring to enable users to safely use their repositories.
As for using other distribution repositories, the DistroExecutionEnvironments page has more information about which container/virtualization systems work with which distribution.
|Repository name||Programs / Packages||Repository type||Licenses requirements||Reliability of license fields||Status|
|Alire||alire (pureOS?)||Ada, SPARK||Not reliable, even allows no license: "The manifest [...] contains [...] information about the crate [...] such as the name and version, others optional like the licenses"|
|ConanCenter||Conan||C/C++ Conan and repository||?||?|
|CPAN||?||Perl||Allow any license (including nonfree software)||?|
|CRAN||?||R||The CRAN policy has strict license requirements, but it also allows the following nonfree licenses:||Very high. See "Source packages" in the CRAN policy.|
(unofficial Guix repository)
|N/A||R||Same as CRAN.||Not referenced by FSDG distributions, so nothing to fix.
Since CRAN licensing information is very strict, it might be very easy to make an FSDG compliant repository out of it, by removing packages with licenses considered nonfree by GNU / The FSF. That repository is already fully automated so it might be very easy to fix and maintain.
|Hackage||Cabal||Haskell||FLOSS license required, points to FSF and OSI for the licenses list.||?|
|PECL||?||PHP||Allow nonfree software, GPL and LGPLv3 (libraries?) not accepted||?|
|Python Package Index||
||Python||Allow any license (including nonfree software)||?||
|RubyGems||rubygems||Ruby||Allow any license (including nonfree software)||?||
|Crates||Cargo||Rust||?||?||lib.rs is a a free frontend to crates so the repository can be viewed without non-free JS.|
Parabola has a bug report (bug #1035) about programming language package managers, it has more reference and information on the issue.
Docker and flatpak registries
See Group:Software/research/ExternalRepositories/DockerRegistries for more details about Docker registries, how to run your own registry easily, etc.
There is also a page about flatpak: Group:Software/research/ExternalRepositories/FlatpakRegistries.
|Repository name||Repository type||Enabled by default?||Licenses requirements||Reliability of license fields||Status||Comments|
|guix-emacs||Guix packages for MELPA||N/A||Same than MELPA?||?||?||The packages are generated automatically, so maybe it's possible somehow to filter-out nonfree software if there is some.|
|ELPA GNU||Emacs Lisp Package Archive||Yes, since emacs 24||Free software||Very strict||FSDG compliant|
|ELPA non-GNU||Emacs Lisp Package Archive||Yes, since emacs 28.1||Free software||Very strict||FSDG compliant|
|MELPA||ELPA-compatible package repository||No||?||?||?|
For known FSDG compliant repositories that have browser addons, see the BrowserAddons wiki page.
|Repository name / URL||Compatible browsers||Licenses requirements||Reliability of license fields||Status||Comments|
|Program name||Program type||Repository type||Repository website||Licenses requirements||Reliability of license fields||Status|
|Arduino||IDE||Repository of software to support microcontroller boards (available in "Boards Manager")||The Arduino IDE has a package manager in "Tools" -> "Board: [...]" -> "Boards Manager".
|Docker||Virtualization software||Repository of distribution installation images and software images||Docker has a default repository for images according to the docker bug #7203 and to a stackoverflow comment. Since that repository is used in the 'docker' command line tool, it needs to be replaced or removed.
|GNOME Boxes (+osinfo-db)||Virtualization software||Repository of distribution installation images that is constructed with libosinfo and osinfo-db||
|Kidad||PCB design software||Repository of Kicad plugins||https://repository.kicad.org/||In tools->Plugin and content manager, there is a package manager of Kicad addons.
|Libreoffice||Document editing software||Extensions||extensions.libreoffice.org||?||?||
|LXC||Virtualization software||Repository of distribution packages / rootfs||images.linuxcontainers.org||?||?||LXC provides $prefix/share/lxc/templates/lxc-download which can download various distributions like Debian, Ubuntu, etc.
|Nextcloud||Collaboration server||Addons||apps.nextcloud.com||?||?||TODO: Check if Nextcloud uses apps.nextcloud.com
|phoronix-test-suite||Performance benchmarking tool||tests||
|Xonotic||Game||Content downloaded during online games:
List of pages
This set of pages talks about external repositories.
(Note that this page does not automatically update; if you add another page under Hardware/, make sure to refresh/purge this page.)
- DistroUpstreamSupport: This page has a list of which FSDG distributions are supported in some of the external repositories present here.
- CrossDistroBootstrap: For how to bootstrap an FSDG distribution from another FSDG compliant distribution.
- Reference: https://www.emacswiki.org/emacs/ELPA
- The repository is hosted in savannah. Since Savannah has extremely strict licensing requirements for hosting, so it should be OK.
"issue" is not in the list (interest, location, project, school) of allowed values for the "Organized around" property.