[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#26256: [PATCH 5/6] gnu: Add userspace-rcu.

From: Marius Bakke
Subject: bug#26256: [PATCH 5/6] gnu: Add userspace-rcu.
Date: Mon, 27 Mar 2017 21:13:40 +0200
User-agent: Notmuch/0.24 ( Emacs/25.1.1 (x86_64-unknown-linux-gnu)

Ludovic Courtès <address@hidden> writes:

> Marius Bakke <address@hidden> skribis:
>> * gnu/packages/linux.scm (userspace-rcu): New variable.
> [...]
>> +    (license
>> +     ;; This library is distributed under LGPL2.1+, but includes some files
>> +     ;; covered by other licenses. The LICENSE file has full details.
>> +     (list license:lgpl2.1+
>> +           license:gpl3+                         ; most tests are gpl2+; 
>> is gpl3+
>> +           license:bsd-2                         ; tests/utils/tap/tap.[ch]
>> +           license:expat                         ; urcu/uatomic/*
>> +           ;; A few files use different variants of the MIT/X11 license.
>> +           (license:x11-style "file://LICENSE"
>> +                              "See LICENSE in the distribution for 
>> details.")))))
> It’s a case where it’d be enough to put lgpl2.1+ and gpl3+ IMO, since
> that’s what effectively applies to the resulting work.

Is this also true for the source code archive itself? As an end user,
looking at the license list and deciding to `guix build -S`, I would
expect the contents to match what's in the package definition.

Is this a distinction we should make? I.e. "source" license vs "product"
license. For Ceph, this would be the current license list in the first
instance and just lgpl2.1 and gpl2 for the built product.

Tricky! Moving the other licenses to the comments for this package, but
something to think about.

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]