I want to add rtklib in repos and I need to Know about allowing it's
license in Fedora.
It is BSD-2-Clause but with addition clause:
- The software package includes some companion executive binaries or shared
libraries necessary to execute APs on Windows. These licenses succeed to the
original ones of these software.
Full text available here
But I am not include any binary or windows specific files in package.
Could you please take a look at bug 1801519?
The package is golang-github-google-licenseclassifier. It contains the text of
a large number of licenses to detect them. Some of these Licenses are good for
Fedora, other not. Basically am I allowed to distribute the text of these
licenses along my package? What it the license status of the text of the
licenses? Is each license covered by itself?
One of the various reasons for having package reviews is having a human
verify that the packager's choice of License: tag is valid. The
Packaging Committee is was faced with a request
(https://pagure.io/packaging-committee/issue/1007) that has us
questioning just how much license review is required.
Are any of the following acceptable?
1) Trust the packager to do a license review, with no reviewer
2) Trust the output of an automated tool which attempts to detect
project licenses (such as askalono).
3) Trust the license tag from a project hosting service such as github?
(I understand that the answer may depend on the hosting service.)
Depending on what is acceptable, we may be able to reduce bureaucracy a
bit. I know that back when I did package reviews, the license review
was often the most difficult part.
On 01. 07. 20 16:24, Ben Cotton wrote:
> == Summary ==
> BLAS/LAPACK packages will be compiled against the FlexiBLAS wrapper
> library, which will set OpenBLAS as system-wide default backend, and
> at the same time will provide a proper switching mechanism that
> currently Fedora lacks.
> == Scope ==
> * Proposal owners: Modify the SPECs of the BLAS/LAPACK-dependent
> packages to build against FlexiBLAS instead of the current backend
> they are using.
I wonder, given FlexiBLAS is released under GPL (and not LGPL), whether this
means we would need to change the licenses of all non-GPL packages that will be
linked to FlexiBLAS to GPL.
On Wed, 1 Jul 2020 19:28:53 +0200
Iñaki Ucar <iucar(a)fedoraproject.org> wrote:
> I'm no expert, but the FAQ says:
> "You have a GPLed program that I'd like to link with my code to build
> a proprietary program. Does the fact that I link with your program
> mean I have to GPL my program? (#LinkingWithGPL)
> Not exactly. It means you must release your program under a license
> compatible with the GPL (more precisely, compatible with one or more
> GPL versions accepted by all the rest of the code in the combination
> that you link). The combination itself is then available under those
> GPL versions."
> So my understanding is that it's ok for a program to link to FlexiBLAS
> if its license is GPL-compatible, not necessarily GPL. But of course
> we would need confirmation from legal.
The library is GPLv3 only
which already makes it incompatible with many GNU Licenses
not to mention many other free licenses that are allowed in Fedora
Fedora Project Contributor