1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
# How to Blacklist a package (adapted from [1]Parabola GNU/Linux-Libre Wiki)
If you find a package that contains, uses or recommends nonfree
software, it should be added to blacklist.txt until a way to free it
is found. More generally, any package in violation to the [2]FSDG
belongs in blacklist.txt.
Other packages should be added to your-privacy-blacklist.txt, if they
endanger privacy, or to your-freedom_emu-blacklist.txt, if they
exist only for the purpose of emulating non-free hardware,
for running other non-free software. See [3] and [4] for more info.
## Reporting a freedom issue
1. Open a bug report on the [5]Parabola Issue Tracker
2. Choose the project responsible for it (usually "Packages")
3. Choose the "Freedom issue" issue concern and priority
4. Include as much detail as possible, as to why the package has freedom issues.
## Blacklisting a package
1. If there is not an existing entry on the [6]LOSTDNRTFSDG wiki, or some other
detailed report which describes the known freedom issues with the package,
open a bug report on the [5]Parabola Issue Tracker as described in the
previous section, if there is not one already. Even if there is some external
bug report to reference, a Parabola ticket is preferred. This will serve as a
discussion thread and reference for the future regarding the package.
2. If possible, start by making a useable liberated [7]replacement package
(packages in your-freedom_emu-blacklist.txt are not meant to have a replacement).
The end result should be a new PKGBUILD in [8]abslibre, and a newly released
replacement package in the repos (usually [libre]).
3. If patching is infeasible, try to find some other program that accomplishes
the same task. There may already be suitable alternative programs in the repos.
4. If no suitable replacement can be made or found, the last resort is to blacklist
the package without a replacement.
5. Clone or pull the latest [9]blacklist.git
6. Add an entry for the package according to the SYNTAX file.
7. Run the ./validate script.
8. Commit and push changes to the server - autobuilder will do the rest.
9. if the push is rejected, you probably forgot step #7
## References:
[1]: https://wiki.parabola.nu/How_to_Blacklist_a_package
[2]: https://www.gnu.org/distros/free-system-distribution-guidelines.html
[3]: https://wiki.parabola.nu/Nonprism
[4]: https://wiki.parabola.nu/Emulator_licensing_issues
[5]: https://labs.parabola.nu
[6]: http://libreplanet.org/wiki/List_of_software_that_does_not_respect_the_Free_System_Distribution_Guidelines#
[7]: https://wiki.parabola.nu/Creating_-libre_packages
[9]: https://git.parabola.nu/abslibre.git
[8]: https://git.parabola.nu/blacklist.git
|
