all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add nlopt.
Date: Sat, 09 Apr 2016 16:38:42 +0200	[thread overview]
Message-ID: <87wpo6n8y5.fsf@gnu.org> (raw)
In-Reply-To: <87a8l5xc9w.fsf@gnu.org> (Roel Janssen's message of "Fri, 08 Apr 2016 00:52:43 +0200")

Hello!

Roel Janssen <roel@gnu.org> skribis:

> I think the licensing page on the website is pretty clear:
> http://ab-initio.mit.edu/wiki/index.php/NLopt_License_and_Copyright
>
> From the page:
>> The NLopt library is under the GNU Lesser General Public License
>> (LGPL), and the copyrights are owned by a variety of authors.
>
> And:
>> The combination of all of this software is under the conjunction of the
>> license terms, and in particular they are limited by the most
>> restrictive of the licenses for the portions, which in this case is the
>> LGPL. (The other portions of NLopt are under LGPL-compatible,
>> less-restrictive licenses like the MIT license. So, if you remove the
>> LGPL portions, which are currently code by Ladislav Luksan, the
>> remainder reverts to a looser license.)

Still, according to luksan/COPYRIGHT, “[s]ubroutines PBUN, PNEW, PVAR,
PSEN” are “for your personal use […] [n]ot for redistribution”.

So my understanding is that we need to remove those four subroutines.
The rest in that directory is LGPLv2.1+.

WDYT?

I don’t see it at
<https://libreplanet.org/wiki/List_of_software_that_does_not_respect_the_Free_System_Distribution_Guidelines>.
Debian has a package: <https://packages.debian.org/source/sid/nlopt>.
Could you check if they apply any patches?

Besides, I suggest reusing the bits about Guile bindings from the patch
I sent.

Thanks,
Ludo’.

  reply	other threads:[~2016-04-09 14:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 11:26 [PATCH] gnu: Add nlopt Roel Janssen
2016-04-07 15:44 ` Leo Famulari
2016-04-07 20:42   ` Alex Kost
2016-04-07 20:49   ` Roel Janssen
2016-04-08 10:18     ` Mathieu Lirzin
2016-04-09  5:56       ` Leo Famulari
2016-04-09 10:54         ` Mathieu Lirzin
2016-04-09 16:21           ` Leo Famulari
2016-04-07 20:48 ` Alex Kost
2016-04-07 21:20   ` Roel Janssen
2016-04-07 21:40 ` Ludovic Courtès
2016-04-07 22:52   ` Roel Janssen
2016-04-09 14:38     ` Ludovic Courtès [this message]
2016-05-03 11:02       ` Roel Janssen
2016-05-03 11:47         ` Ludovic Courtès
2016-05-03 12:34           ` Roel Janssen
2016-05-03 20:02             ` Ludovic Courtès
2016-05-03 20:17               ` Roel Janssen
2016-05-04  8:38                 ` Alex Kost
2016-05-04  8:52                   ` Roel Janssen

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=87wpo6n8y5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=roel@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.