From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add libiax
Date: Tue, 31 May 2016 20:40:53 +0300 [thread overview]
Message-ID: <20160531174053.GD13578@debian-netbook> (raw)
In-Reply-To: <20160531162555.GA32099@jasmine>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
On Tue, May 31, 2016 at 12:25:55PM -0400, Leo Famulari wrote:
> On Mon, May 30, 2016 at 02:50:02PM -0500, Lukas Gradl wrote:
> > * gnu/packages/telephony.scm (libiax): New variable.
>
> > + (license lgpl2.0))))
>
> In my final review, I found that some source files are licensed under
> the GPL (no version specified) as well as one public-domain file. The
> details are in the attached patch revision.
>
> Since I don't understand the fine points of these things, I ask the
> group: can a source distribution be LGPL 2.0 and include GPL components?
I saw it explained another time that if the license is just "GPL" then
we can read it as we see fit, which usually means GPL3+ (for those
portions).
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-05-31 17:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 23:08 [PATCH] Add libiax Lukas Gradl
2016-05-29 0:48 ` Leo Famulari
2016-05-30 19:47 ` Lukas Gradl
2016-05-31 19:02 ` Andreas Enge
2016-05-31 21:02 ` Leo Famulari
2016-06-01 14:40 ` Lukas Gradl
2016-06-02 1:44 ` Leo Famulari
2016-05-29 0:55 ` Leo Famulari
2016-05-30 19:50 ` Lukas Gradl
2016-05-31 16:25 ` Leo Famulari
2016-05-31 17:40 ` Efraim Flashner [this message]
2016-05-31 19:13 ` Andreas Enge
2016-05-31 21:01 ` Leo Famulari
2016-05-31 20:59 ` Leo Famulari
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=20160531174053.GD13578@debian-netbook \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.