all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/4] gnu: Add r-bigmemory-sri.
Date: Thu, 03 Nov 2016 16:41:02 +0100	[thread overview]
Message-ID: <87eg2sinap.fsf@elephly.net> (raw)
In-Reply-To: <87ins4mxzn.fsf@gnu.org>


Roel Janssen <roel@gnu.org> writes:

> Ricardo Wurmus writes:
>
>> Roel Janssen <roel@gnu.org> writes:
>>
>>> Roel Janssen writes:
>>>
>>>> Ricardo Wurmus writes:
>>>>
>>>>> Roel Janssen <roel@gnu.org> writes:
>>>>>> +    (description "This package provides a shared resource interface for the
>>>>>> +bigmemory and synchronicity packages.")
>>>>>> +    (license (list license:lgpl3 license:asl2.0))))
>>>>>
>>>>> What does this list mean?
>>>>> Also: is this LGPL3+ or LGPL3 only?
>>>>
>>>> The CRAN page lists LGPL3 explicitly, but that could be imprecise ...
>>>> The source code package does not contain any other license indication
>>>> than waht is stated in the DESCRIPTION file (which states LGPL3 and
>>>> Apache Software License 2.0).
>>>>
>>>> See:
>>>>   https://cran.r-project.org/web/packages/bigmemory.sri/
>>>>
>>>> So, I think the only thing I can do is just follow what has been stated,
>>>> which is LGPL3 (precisely this) and Apache Software License 2.0.
>>>
>>> I don't know how to proceed now.  I think it's fine as the list of
>>> licenses is the list of licenses they provide.
>>>
>>> Are these licenses incompatible?  If so, then there's nothing I can do
>>> either, because these are the licenses that are provided..
>>
>> Usually, what we do for R is to assume “or later” because that’s how
>> things are usually done on CRAN.  (They also automatically expand
>> license declarations.)
>
> Well I don't think we can do that in this case because that's not what
> the license field says.  In the code there's no license at all, so that
> makes it even more difficult.

You’re right.  I misremembered.  It’s only these joint license
declarations like “GPL-2 | GPL-3” that effectively mean “or later”.  (It
is impossible to express “or later” in canonical R license fields.)

> I guess this is about the possible license incompatibility between LGPLv3
> and Apache?  I tried to explain that in any case, there's nothing I can
> do about it anyway..

Actually, the declaration in this package means “either this or that”
license.

See https://cran.r-project.org/doc/manuals/R-exts.html#The-DESCRIPTION-file

    “The mandatory ‘License’ field in the DESCRIPTION file should
     specify the license of the package in a standardized
     form. Alternatives are indicated via vertical bars.”

Your patch is fine if you add a comment above the license field that
states that these one of these two licenses may be choosen.

~~ Ricardo

  reply	other threads:[~2016-11-03 15:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 12:26 [PATCH 2/4] gnu: Add r-bigmemory-sri Roel Janssen
2016-10-28 20:44 ` Ricardo Wurmus
2016-10-31  9:18   ` Roel Janssen
2016-11-03 13:33     ` Roel Janssen
2016-11-03 14:19       ` Ricardo Wurmus
2016-11-03 14:36         ` Roel Janssen
2016-11-03 15:41           ` Ricardo Wurmus [this message]
2016-11-04 13:15             ` Roel Janssen
2016-11-04 13:21               ` Ricardo Wurmus

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=87eg2sinap.fsf@elephly.net \
    --to=rekado@elephly.net \
    --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.