From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 41118@debbugs.gnu.org
Subject: [bug#41118] [PATCH] gnu: inkscape: Update to 1.0.
Date: Fri, 15 May 2020 23:53:24 -0400 [thread overview]
Message-ID: <87ftc0bknf.fsf@gmail.com> (raw)
In-Reply-To: <20200515144324.GA18054@jasmine.lan> (Leo Famulari's message of "Fri, 15 May 2020 10:43:24 -0400")
Hello Leo,
Leo Famulari <leo@famulari.name> writes:
> On Fri, May 15, 2020 at 09:36:13AM -0400, Maxim Cournoyer wrote:
>> This was made here: https://gitlab.com/inkscape/inkscape/-/issues/784.
>> If you have a good grasp of the GPL v2 vs GPL v3 merits, perhaps it'd be
>> useful to them to to post that there. IIRC, I think the big new things
>> in GPL v3 were immunization to patent attacks (nice to have for
>> Inkscape) as well as preventing tivoization (this is not so applicable),
>> and clarifying that linking with GPL code means the whole should be GPL.
>> I'll re-read the licenses text in detail when I have a chance.
>>
>> Anyway, if this doesn't move quickly enough, we could reluctantly build
>> Inkscape with its bundled lib2geom, which is a subset of the full
>> lib2geom and which doesn't link with GSL (IIRC).
Actually, this doesn't help with the licensing incompatibility, given
that Inkscape already depends on the GPL v3+ GNU Scientific Library
(GSL) and that the bundled lib2geom sources within Inkscape make use of
GSL. I've pointed that here:
https://gitlab.com/inkscape/inkscape/-/issues/784#note_343667232.
> In <https://gitlab.com/inkscape/inkscape/-/issues/784#note_343293612>
> they seem to demonstrate a misunderstanding about lib2geom's license.
> That commenter thinks that lib2geom is GPL2+, when it's actually
> LGPL-2.1 or MPL-1.1.
I've brought this to their attention, thank you.
> However, gnu.org says that LGPL-2.1 is compatible with GPL2 and GPL3. So
> maybe it's fine; I don't know. I think we should ask FSF for advice
> <https://www.fsf.org/licensing>.
That's a good idea.
Maxim
next prev parent reply other threads:[~2020-05-16 3:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 3:23 [bug#41118] [PATCH] gnu: inkscape: Update to 1.0 Maxim Cournoyer
2020-05-07 4:37 ` [bug#41118] [PATCH V2] " Maxim Cournoyer
2020-05-07 15:20 ` [bug#41118] [PATCH] " Leo Famulari
2020-05-15 13:36 ` Maxim Cournoyer
2020-05-15 14:43 ` Leo Famulari
2020-05-16 3:53 ` Maxim Cournoyer [this message]
2020-05-16 11:05 ` Marius Bakke
2020-05-16 18:59 ` Maxim Cournoyer
2020-05-07 15:27 ` Leo Famulari
2020-05-07 15:30 ` Leo Famulari
2020-05-28 3:34 ` Maxim Cournoyer
2020-05-28 13:39 ` Leo Famulari
2020-06-01 3:14 ` bug#41118: " Maxim Cournoyer
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=87ftc0bknf.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=41118@debbugs.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 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).