SYNTAX 3.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677
  1. The *blacklist.txt files consist of lines in the following format:
  2. original-package:[libre-replacement]:ref:id:short-description
  3. * 'original-package' is the name of the binary package from Arch
  4. * 'libre-replacement' is the name of the binary package that provides
  5. and replaces the original-package, or empty if there is no
  6. compatible replacement. The replacement must be compatible for use
  7. by humans and scripts, e.g. fastjar is not a replacement for zip
  8. although both solve the same problem. Packages in
  9. your-freedom_emu-blacklist.txt are not meant to have a replacement.
  10. * 'ref' is one of the keys in the first column in following table:
  11. debian : http://bugs.debian.org/
  12. fsf : http://libreplanet.org/wiki/List_of_software_that_does_not_respect_the_Free_System_Distribution_Guidelines#
  13. savannah : https://savannah.nongnu.org/bugs/?
  14. fedora : https://bugzilla.redhat.com/show_bug.cgi?id=
  15. parabola : https://labs.parabola.nu/issues/
  16. The URL in the second column in above table, when concatenated with
  17. the value of the 'id' field should form a valid URL pointing to an
  18. associated ticket on the web.
  19. We should prefer FSF refs, since they are easily available for other
  20. distros. Hopefully some lines will move from parabola:X to fsf:Y with
  21. the LibrePlanet wiki linking to the X issue on labs.parabola.nu.
  22. * 'id' refers to a reported bug on the tracker indicated in the 'ref' column
  23. The URL in the second column in 'ref' table, when concatenated with
  24. the value of this 'id' field should form a valid URL pointing to a
  25. ticket on the web that describes the reason for the package being blacklisted,
  26. and when applicable, whatever liberation procedure was used
  27. to create a replacement package.
  28. * 'short-description' categorizes original-package with some tags,
  29. followed by a short verbal explanation. Popular tags are:
  30. [nonfree]·······This package is blatently non-free software.
  31. [semifree]······This package is mostly free, but contains some non-free
  32. software or documentation.
  33. [uses-nonfree]··This package depends on, recommends, or otherwise
  34. inappropriately integrates with other non-free software
  35. or services.
  36. [branding]······This package has branding needs adjusted; it refers to
  37. "Arch" instead of "Parabola", or "Linux" instead of
  38. "GNU/Linux", etc.
  39. [technical]·····This package cannot be imported from Arch because of
  40. technical reasons, rather than freedom reasons; this is
  41. NOT to do with freedom or privacy issues in the
  42. package. This usually comes down to two things: it
  43. must be recompiled against our version of a dependency
  44. package, or it must be compiled from source, as we are
  45. stricter about that than Arch is.
  46. If this tag is present, then either the libre-replacement
  47. column should match the the original-package column;
  48. or the [FIXME:package] tag should also be present and
  49. the libre-replacement column should be empty.
  50. [FIXME:package] This package has a free replacement, or could be built
  51. in a way that is acceptable, but no one has done so yet.
  52. [FIXME:description] Someone needs to fix the description in blacklist.txt
  53. To make reporting issues to gnu-linux-libre easier, we should indicate
  54. in the description if the package is blacklisted due to an upstream FSDG
  55. issue, problem introduced by Arch (e.g. not including required license
  56. text, adding optional dependency on a non-free package), or just
  57. branding, dependency or non-freedom-related issues which don't need
  58. reporting to other distros.