all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Craven <david@craven.ch>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: License auditing
Date: Wed, 3 Aug 2016 20:05:39 +0200	[thread overview]
Message-ID: <CAL1_imnUxJwfAJdmaqmVQrBhvLaymSGOt22jBLVmgtz883x6bg@mail.gmail.com> (raw)
In-Reply-To: <20160803195511.3f55fc92@scratchpost.org>

>> How can I tell the difference between a lgpl2.1 and lgpl2.1+ license?
>"or later"

Yes, I get that, but does it explicitly say the words "or latter" in the license
text? What about when there are lgpl2, lgpl2.1 and lgpl3 license files in
the repo? Is that (list lgpl2.0 lgpl2.1 lgpl3) or lgpl2.0+?

> I could do that program in maybe 2 hours and find and extract all the
> official license texts in a few more hours. But does such a thing already
> exist? [Seems like something obvious to have and I'm writing many other
> things already.]

I only found this, which only detects 3 license types.
https://github.com/tantalor/detect-license

  parent reply	other threads:[~2016-08-03 18:05 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 [this message]
2016-08-03 18:15     ` David Craven
2016-08-03 18:03 ` Leo Famulari
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

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

  git send-email \
    --in-reply-to=CAL1_imnUxJwfAJdmaqmVQrBhvLaymSGOt22jBLVmgtz883x6bg@mail.gmail.com \
    --to=david@craven.ch \
    --cc=dannym@scratchpost.org \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.