From: Leo Famulari <leo@famulari.name>
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: License auditing
Date: Wed, 3 Aug 2016 14:03:42 -0400 [thread overview]
Message-ID: <20160803180342.GA11621@jasmine> (raw)
In-Reply-To: <CAL1_im=8gC_Dq4YYn6vstB=vq6VPWPRvp65MgSedUiHYkO29DQ@mail.gmail.com>
On Wed, Aug 03, 2016 at 06:28:38PM +0200, David Craven wrote:
> Hi!
>
> How can I tell the difference between a lgpl2.1 and lgpl2.1+ license?
The license headers in the source files will say if they are licensed
under version 2.1 or later. Something like this:
"...either version 2.1 of the License, or (at your option) any later
version."
I've heard that if the only license information is a copy of the full
license (for example, in LICENSE or COPYING) and the files have no
license headers, then the "or later" part is implied, but I'm not sure.
> Is this a job that an automated tool could do? Detecting licenses
> included in a tarball?
A tool might be able to suggest something, but I think that it will
always require human inspection. And we only have to do this inspection
once per package version, on behalf of everybody else that uses the
distribution.
next prev parent reply other threads:[~2016-08-03 18:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 16:28 License auditing David Craven
2016-08-03 17:55 ` Danny Milosavljevic
2016-08-03 18:00 ` Jelle Licht
2016-08-03 18:05 ` Leo Famulari
2016-08-03 18:05 ` David Craven
2016-08-03 18:15 ` David Craven
2016-08-03 18:03 ` Leo Famulari [this message]
2016-08-03 20:42 ` Ludovic Courtès
2016-08-03 21:11 ` Alex Griffin
2016-08-03 22:59 ` David Craven
2016-08-04 14:23 ` Ludovic Courtès
2016-08-04 14:40 ` Alex Griffin
-- strict thread matches above, loose matches on Subject: below --
2016-08-04 17:41 Philippe Ombredanne
2016-08-04 18:34 Philippe Ombredanne
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=20160803180342.GA11621@jasmine \
--to=leo@famulari.name \
--cc=david@craven.ch \
--cc=guix-devel@gnu.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.
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).