Enlightenment 16 uses a modified (non-standard) MIT license that
includes an advertising clause. (This makes it incompatible with the
GPL.) I've named it enlightenment16 to differentiate that Enlightenment
>=17 releases use the 2-Clause BSD. (Enlightenment 16 continues to be
developed independently, and is of current interest to pkgsrc users.)
In some places, this is referred to as the "MIT With Advertising"
license, but I'm not aware of other projects using this variant. If it
becomes more broadly relevant to pkgsrc, we could rename it such.
(This should have been added a long time ago, the wm/enlightenment
package simply has never had a LICENSE variable set. Better late than
never.)
The biopython license is _very_ similar, but not identical, to many
other open source licenses used throughout pkgsrc. The gratuitous
differences are being addressed by the project through an effort to
relicense all files to the 3-clause BSD license. In the meantime,
Debian has accepted that the current biopython license meets the DFSG
and includes the package in their main distribution. Consequently,
rename the license file and add it to DEFAULT_ACCEPTABLE_LICENSES.
See http://mail-index.netbsd.org/pkgsrc-changes/2019/08/13/msg195804.html.
(This is a comment-only change.)
Add compliance with Debian Free Software Guidelines as evidenced by
inclusion in Debian main as a basis for inclusion in
DEFAULT_ACCEPTABLE_LICENSES.
Clarify that the exclusion of AGPL by TNF board is higher priority
than the new DFSG section.
Add to the "obviously would be approved as Free" section the notion
that a license must also obviously not trigger the AGPL concern.
As proposed on tech-pkg, edited based on agc@ comments.
Up to now, there was a central list of variable name patterns that
defined whether a variable was printed as a sorted list, as a list or as
a single value.
Now each variable group decides on its own which of the variables are
printed in which way, using the usual glob patterns. This is more
flexible since different files sometimes differ in their naming
conventions.
Two variable groups are added: license (for everything related to
LICENSE) and go (for lang/go).
Ninka can be installed from wip/ninka and analyzes each file individually,
thereby providing a much more detailed analysis than the ad-hoc method that
only looks at some COPYING files.
If Ninka is not installed, the naive fallback continues to be used.
Before, the first file that looked like a license file was considered.
The others were completely ignored. This led to a wrong license for
cross/arm-none-eabi-gcc. To prevent these cases in the future, the license
is only guessed if there is exactly one file with a typical license name.
This approach is still naive, but at least a little more precise. Replacing
the guess-license with a determine-licenses is much more complicated
though, since each source code file may have its own license declared, and
handling all these special cases leads to very complex license expressions
(like "gnu-gpl-v3 for all files, except for special.c, which is apache-2.0
or mit). This is very hard to do correctly.
It compares the license file from the package with the available licenses
in licenses/ and shows the diff to the best match.
This will hopefully make it easier for package authors to include the
LICENSE variable in the package Makefile. This variable being missing is
one of the most frequent error messages from pkglint (4187 out of 20044).
http://ctan.org/license/gfsl
Since this is basically the LaTeX Project Public License with one clause
removed, add it to the default acceptable licenses.
(lppl is fine with both OSI and FSF and already allowed.)
