From: Dave Love <fx@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Question about multiple licenses
Date: Tue, 12 Sep 2017 23:13:42 +0100 [thread overview]
Message-ID: <87vaknh8fd.fsf@albion.it.manchester.ac.uk> (raw)
In-Reply-To: <87zia246lw.fsf@gnu.org> ("Ludovic \=\?iso-8859-1\?Q\?Court\=E8s\?\= \=\?iso-8859-1\?Q\?\=22's\?\= message of "Sun, 10 Sep 2017 22:54:35 +0200")
Ludovic Courtès <ludo@gnu.org> writes:
>> Well, from what I know about copyright, that isn't the licence of glibc,
>> which is the sum of all the licences involved, and you'd have to know
>> how to find them if you didn't just unpack the tarball. With pack
>> output in a lot of cases you don't have the information.
>
> Right, ‘guix pack’ makes things more complicated—although I would argue
> that, contrary to Dockerfiles and the like (which nobody seems to
> complain about),
Well,
they should -- I think there should be something from GNU on
the topic -- and it's what motivated the Fedora
policy to separate %licence. That's supposed to go into containers as
I understand it, c.f. %doc, which isn't in spec files.
> Guix makes it easier to do provenance tracking since
> there’s an unambiguous source → binary mapping.
Right, though the binary can be under a subset licence, e.g. when
un-shipped tests are under a different licence.
> How do Debian and Fedora determine the relevant files to copy? We could
> investigate ways to do that, but it won’t scale unless we have a mostly
> automated way to do it.
The submitter and reviewer have to put the right stuff in the package
definition -- %license for Fedora and the copyright file for Debian.
That should be checked to first order with licensecheck (automated in
the "fedora-review" tool). You might be able to automate cross-checking
with Debian and Fedora to some extent.
> (It won’t scale to the size of Stackage, CPAN, Pypi, etc. either…)
>
> Thoughts?
I think it has to be got right even if they don't do so. There's plenty
imported to Fedora and Debian from those.
prev parent reply other threads:[~2017-09-12 22:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 7:40 Question about multiple licenses Arun Isaac
2017-08-28 10:45 ` Alex Vong
2017-08-28 17:25 ` Arun Isaac
2017-08-28 17:29 ` Efraim Flashner
2017-08-29 6:30 ` Arun Isaac
2017-09-01 11:43 ` Dave Love
2017-09-02 16:54 ` Alex Vong
2017-09-07 16:21 ` Dave Love
2017-09-03 11:45 ` Arun Isaac
2017-09-04 14:57 ` Ludovic Courtès
2017-09-07 16:20 ` Dave Love
2017-09-10 20:54 ` Ludovic Courtès
2017-09-11 11:29 ` Alex Vong
2017-09-11 12:45 ` Andy Wingo
2017-09-12 22:15 ` Dave Love
2017-09-12 22:13 ` Dave Love [this message]
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=87vaknh8fd.fsf@albion.it.manchester.ac.uk \
--to=fx@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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.