unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>, 50347@debbugs.gnu.org
Cc: guix-devel@gnu.org
Subject: Re: [bug#50347] [RFC PATCH] lint: Warn about kernel modules with a suspect license.
Date: Mon, 06 Sep 2021 10:23:52 +0200	[thread overview]
Message-ID: <868s0ajenb.fsf@gmail.com> (raw)
In-Reply-To: <5c4caf742c5dbe2a02aede2b20ff80eae7bc352a.camel@telenet.be>

Hi Maxime,

On Thu, 02 Sep 2021 at 23:42, Maxime Devos <maximedevos@telenet.be> wrote:

> This patch adds a 'suspect-license' linter detecting some suspicious
> values in the license fields of linux modules:

I do not know if it is worth to add a linter for really few corner
cases, IMHO.

> For zfs, the issue is the CDDL license.  For the others, the issue
> is the gpl3+ license.  See the article by the SFLC for why this linter
> detets ZFS:
>
> <https://sfconservancy.org/blog/2016/feb/25/zfs-and-linux/#footnote-other-ZFS-copyright-holders>.

The issue is about distributing binaries, IIUC.  From my point of view,
a such linter should check X-license packages using any build-system but
“linked“ to incompatible X-license packages.  Well, I do not know if it
is worth to automate this since it appears to me really sparse corner
cases.

Cheers,
simon


  parent reply	other threads:[~2021-09-06  8:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02 21:42 [bug#50347] [RFC PATCH] lint: Warn about kernel modules with a suspect license Maxime Devos
2021-09-02 22:20 ` Maxime Devos
2021-09-06  8:23 ` zimoun [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-04 18:04 raid5atemyhomework

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=868s0ajenb.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=50347@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).