[Dev] [RFC] Package freedom requirements clarification

Michał Masłowski mtjm at mtjm.eu
Sun Nov 25 10:29:46 GMT 2012

>> 0. Do not fetch nonfree sources in PKGBUILDs
>> I believe this is needed for FSDG compliance.  This can be implemented
>> using SRCBUILDs or similar technologies.  Having patches containing
>> whole nontrivial nonfree files in abslibre is IMO also not acceptable.
> I'd like to change this to:
>  0.1. There should be no nonfree code by the end of `makepkg -o`"
>  0.2. Nothing nonfree should be tracked in ABSLibre/PBS

It's the same, more explicit.

> Right now 0.1 means what you have; but the next version of makepkg
> offers a `prepare()` function to prepare the sources.  It works exactly
> like our `mksource()` (currently deprecated in favor of `SRCBUILD`).

The documentation suggests it being used after the source is extracted,
while mksource and SRCBUILDs do this to make the source archive used for
builds.  Does this mean that our source mirrors would provide the
nonfree files removed in prepare()?

> I added 0.2 to mean that there can't be a patch file containing
> non-free code.  Which means that we must use `rm` and friends to
> remove non-free code; which is fine in most cases.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20121125/54607310/attachment.sig>

More information about the Dev mailing list