[aur-requests] [PRQ#6184] Deletion Request for ffmpeg-full-nvenc

Dmitriy Kharitonov darksab0r at gmail.com
Sun Aug 14 21:15:51 UTC 2016

I guess this request should apply to all aur/ffmpeg-full* packages, as they
share the same licensing scheme in their PKGBUILDs.

Most files in FFmpeg are under LGPL, some optional parts (which are enabled
by default in this PKGBUILD) are under GPL. Also, this PKGBUILD includes
some options which enable combining with GPL-incompatible external
libraries, causing the resulting binary to be unredistributable. The latter
is mentioned in UNREDISTRIBUTABLE.txt enclosed with the AUR package.

Now I am seeking clarification of license arrays in AUR PKGBUILDs. Should
they include only the license of the resulting package as a whole (so, the
most restrictive license among its parts)? What are the use cases of
multiple license entries, which are mentioned in wiki
<https://wiki.archlinux.org/index.php/PKGBUILD#license>? Also, I guess,
license in PKGBUILD should be set according to configure options
pre-defined by package maintainer, so if some user wants to delete or add
the "--use-non-free" line, they should change the license by themselves,
but what if the license of the resulting package is decided by the presence
of some optdepend library autodetected by ./configure?

Finally, I'd be very grateful to to see more coverage of licensing issues
in Arch wiki and guides. This area is complicated enough as it is, and
applying it to Arch LInux packaging is even more tricky for me.

On Sun, Aug 14, 2016 at 10:47 PM, <notify at aur.archlinux.org> wrote:

> FredBezies [1] filed a deletion request for ffmpeg-full-nvenc [2]:
> Nonsense in Licenses entry : "GPL, custom:unredistributable "
> How can you mix both GPL and a non-free license in the same time ?
> [1] https://aur.archlinux.org/account/FredBezies/
> [2] https://aur.archlinux.org/pkgbase/ffmpeg-full-nvenc/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.archlinux.org/pipermail/aur-requests/attachments/20160815/81d77211/attachment.html>

More information about the aur-requests mailing list