Group: Software/FSDG distributions

From LibrePlanet
Jump to: navigation, search
(Policies: Replicant: binary packages: move details to references)
(Policies: fix typo)
Line 175: Line 175:
 
! Replicant
 
! Replicant
 
| Unknown (no decision)
 
| Unknown (no decision)
| No<ref>Even if binary packages are allowed, Replicant still needs to ship the complete and corresponding source code of binary packages as well, otherwise this would make the package nonfree and/or create license compliance issues for Replicant.</pre>
+
| No<ref>Even if binary packages are allowed, Replicant still needs to ship the complete and corresponding source code of binary packages as well, otherwise this would make the package nonfree and/or create license compliance issues for Replicant.</ref>
 
|
 
|
 
| To support a device, Replicant requires:
 
| To support a device, Replicant requires:

Revision as of 10:42, 5 January 2023

Introduction

This page can track some differences between FSDG compliant distributions.

This could help see if FSDG distributions can collaborate more on some topics.

Documentation

Distribution Documentation Wiki
Link License Link License Software
N/A Libreplanet GFDL 1.3+ and copyright assignment Mediawiki
Dragora No Wiki found
Dynebolics No Wiki found
Guix GFDL 1.3 (+?) libreplanet.org/wiki/Group:Guix GFDL 1.3+ and copyright assignment Mediawiki
Hyperbola wiki.hyperbola.info CC BY-SA 4.0 Dokuwiki10
LibreCMC librecmc.org/fossil CC BY-SA 4.0 Fossil
Parabola wiki.parabola.nu CC BY-SA 4.0 Mediawiki
ProteanOS Ikiwiki
PureOS
Replicant CC BY-SA 3.0 Redmine, migration to Mediawiki planned.
Trisquel
Ututo

Policies

While FSDG compliant distributions need to follow the Free System Distribution Guidelines, they can also have additional policies that are more strict on other aspects.

Knowing that not only enables to choose the most adapted FSDG distribution to one's needs, but it is also important to keep in mind when trying to build cross-distribution collaboration.

For instance non-functional data licensed under the CC-BY-ND licenses is not allowed in Parabola but it might be allowed in other FSDG compliant distributions, so what might be a bug in Parabola is not necessarily a bug in other distributions.

Distribution Free culture Require package to be built from source Reuse packages or binaries Computer support
Dragora
Dynebolics
Guix Yes Only to build some compilers. No restrictions
Hyperbola Yes[1]
LibreCMC
Parabola Yes Yes[2] Reuse some packages from various distributions:
  • Arch Linux
  • Arch Linux ARM
  • Arch Linux 32
Restrictions exist only for official support for ARM computers:
  • Requires a free software bootloader
  • Requires documentation in the wiki
  • Requires a package to ship the bootloader
ProteanOS
PureOS
Replicant Unknown (no decision) No[3] To support a device, Replicant requires:
  • an isolated modem
  • a replaceable battery
  • to be able to install Replicant without nonfree software
Trisquel
Ututo

References

  1. https://wiki.hyperbola.info/doku.php?id=en:philosophy:chromium_flaws mentions that we (hyperbola) "require all software to be built from source
  2. The documentation on Parabola blacklist format mention that blacklisting Arch Linux packages not built from source (by Arch Linux) need to be removed or replaced as the packages "must be compiled from source, as we are stricter about that than Arch is". Packages not build from source are package whose package definition download binaries and package the binaries.
  3. Even if binary packages are allowed, Replicant still needs to ship the complete and corresponding source code of binary packages as well, otherwise this would make the package nonfree and/or create license compliance issues for Replicant.