From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [RFC] Solving the problem of huge number of wrong LICENSES=*GPL-[23]
Date: Fri, 31 Aug 2018 18:31:46 -0400 [thread overview]
Message-ID: <CAGfcS_nLnzUYG1SfCir8251PYPDCbveMAs-k0vDwPXKBjVbYsA@mail.gmail.com> (raw)
In-Reply-To: <4004237.4pTCg0tAxr@saffron>
On Mon, Aug 27, 2018 at 6:46 PM Michael Mol <mikemol@gmail.com> wrote:
>
> I can say that if the licenses are habitually misidentified, I could not use
> Gentoo's portage tree in my job without extensive and ongoing revalidation of
> the license metadata.
>
Keep in mind that we're just talking about GPL-2 vs 2+ and GPL-3 vs
3+. We're not talking about GPL vs BSD vs something that involves a
EULA.
Do you actually accept one of these without the other, such that you
would have problems if they had gotten confused?
--
Rich
next prev parent reply other threads:[~2018-08-31 22:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 10:39 [gentoo-dev] [RFC] Solving the problem of huge number of wrong LICENSES=*GPL-[23] Michał Górny
2018-08-26 10:53 ` Mart Raudsepp
2018-08-26 11:09 ` Paweł Hajdan, Jr.
2018-08-26 11:15 ` Michał Górny
2018-08-26 11:33 ` Roy Bamford
2018-08-26 11:35 ` Rich Freeman
2018-08-26 17:03 ` Paweł Hajdan, Jr.
2018-08-27 22:46 ` Michael Mol
2018-08-31 22:31 ` Rich Freeman [this message]
2018-09-01 7:44 ` Paweł Hajdan, Jr.
2018-08-26 15:50 ` Ulrich Mueller
2018-08-26 17:14 ` Michał Górny
2018-08-26 18:14 ` Mart Raudsepp
2018-08-26 19:43 ` M. J. Everitt
2018-08-26 19:45 ` Francesco Riosa
2018-08-26 19:50 ` Francesco Riosa
2018-08-26 22:40 ` Jonas Stein
[not found] ` <3116195.kUm3yr6LE6@hermes>
2018-08-26 22:41 ` Robin H. Johnson
2018-08-27 2:55 ` Ulrich Mueller
[not found] ` <3623085.8soZgasqjt@hermes>
2018-08-27 7:35 ` Ulrich Mueller
2018-08-27 2:37 ` Ulrich Mueller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGfcS_nLnzUYG1SfCir8251PYPDCbveMAs-k0vDwPXKBjVbYsA@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox