From: Marius Bakke <marius@gnu.org>
To: Alexandros Theodotou <alex@zrythm.org>, 42279@debbugs.gnu.org
Subject: [bug#42279] [PATCH] gnu: Add distrho-ports.
Date: Tue, 21 Jul 2020 00:59:06 +0200 [thread overview]
Message-ID: <87zh7tg5dx.fsf@gnu.org> (raw)
In-Reply-To: <86aadb3670706e4645ee98b2455b18c57bba48cd.camel@zrythm.org>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
Alexandros Theodotou <alex@zrythm.org> writes:
> Hi,
>
> Thanks for the review.
>
> On Tue, 2020-07-21 at 00:07 +0200, Marius Bakke wrote:
>> > + Wolpertinger.")
>> > + (home-page "http://distrho.sourceforge.net/ports")
>> > + (license (list license:gpl2 ; found in doc directory
>> > + license:lgpl3+ ; found in doc directory
>> > + license:gpl3))))) ; mentioned in meson file
>>
>> This is a problem: GPL3 is famously incompatible with GPL2. If these
>> plugins are licensed separately it would be good to list the license
>> for
>> each and take it from there.
>>
>> Even better (I think?) is to package each plugin separately. Then
>> users
>> can choose whether to combine these incompatibly-licensed plugins,
>> but
>> we as a distribution can not (and probably not DISTRHO either).
>>
>> Not sure what to do about it. Ideas?
>
> Why is it a problem? It's only a problem if you link them together
> afaik. The plugins that this project produces are all separate
> binaries, each under its own license.
Right. If they don't share code it's probably okay.
> I think we should just list the license for each included plugin. I'm a
> bit against making separate packages - it would be a pain to maintain
> and the plugins don't take up much disk space.
Listing the license of each plugin sounds good to me.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-07-20 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 21:27 [bug#42279] [PATCH] gnu: Add distrho-ports Alexandros Theodotou
2020-07-20 22:07 ` Marius Bakke
2020-07-20 22:24 ` Alexandros Theodotou
2020-07-20 22:59 ` Marius Bakke [this message]
2021-01-04 11:30 ` Alexandros Theodotou
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=87zh7tg5dx.fsf@gnu.org \
--to=marius@gnu.org \
--cc=42279@debbugs.gnu.org \
--cc=alex@zrythm.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).