License list synchronization for rpminspect
by David Cantrell
Hi,
rpminspect performs a License tag validation on packages. The license data
comes from a JSON data file that I think was produced at some point from the
Fedora charts on the wiki but then never really updated. Consequently, it
raises failures that are incorrect per current licensing data.
The data for rpminspect comes from:
https://github.com/rpminspect/rpminspect-data-fedora
The license data is in licenses/fedora.json
The format should be somewhat easy to understand. I didn't create it. I
found this database and ran with it. I'd like to come up with a way to keep
it in sync with the data on the wiki. Right now I advise package maintainers
to send me pull requests to update the data, but that's not going to be a long
term solution.
Anyone have any thoughts on this? Ideas of how to keep the information up to
date in all locations?
Thanks,
--
David Cantrell <dcantrell(a)redhat.com>
Red Hat, Inc. | Boston, MA | EST5EDT
1 month, 1 week
Open CASCADE Technology licence for versions 6.7.0 and later.
by Przemo Firszt
There was a change of OCCT licence for version 6.7.0. It's LGPL + additional clause. The full text is here: https://fedoraproject.org/wiki/Licensing/Open_CASCADE_Technology_Public_L... The additional clause:
Open CASCADE Exception (version 1.0) to GNU LGPL version 2.1.
The object code (i.e. not a source) form of a "work that uses the Library" can incorporate material from a header file that is part of the Library. As a special exception to the GNU Lesser General Public License version 2.1, you may distribute such object code incorporating material from header files provided with the Open CASCADE Technology libraries (including code of CDL generic classes) under terms of your choice, provided that you give prominent notice in supporting documentation to this code that it makes use of or is based on facilities provided by the Open CASCADE Technology software.
Is it a show stopper for fedora?
1 month, 2 weeks
