unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Jam: which licence is this?
Date: Sun, 25 Apr 2021 16:37:42 -0400	[thread overview]
Message-ID: <87h7juje1a.fsf@netris.org> (raw)
In-Reply-To: <YIWoR/K8IgSNQww/@jasmine.lan>

Hi Leo,

Leo Famulari <leo@famulari.name> writes:

> On Sun, Apr 25, 2021 at 01:25:21PM -0400, Mark H Weaver wrote:
>> In general, I think that the license field of a package should include
>> all licenses that cover any files in its source distribution (by which I
>> mean the output of "guix build --source").
>> 
>> My rationale is that it is the source code, and not merely the build
>> outputs, where users will want to exercise the four freedoms of free
>> software.  For example, when a user wishes to study, modify, or
>> redistribute the software, they will want to be able to do those things
>> with the entire source distribution.
>> 
>> Does that make sense?  What do you think?
>
> It makes sense, but we've never done that.
>
> For example, the autotools files such as configure.ac bear a simple
> permissive license, but we do not mention that in the license field of
> the 'hello' package.
>
> Instead, we typically use the license that covers the overall program,
> not the (sometimes dozens of) licenses of every single file in the
> source distribution.

You're right, and that's a good point.  It's true that Guix has a
longstanding practice of omitting more lax licenses when there's also a
more restrictive license covering the same package.  I should have
mentioned that.

However, I think that longstanding practice is orthogonal to the
question of whether licenses covering build system components can be
omitted from the 'license' field.

> Can you clarify your expectations regarding which files' licenses should
> be mentioned in the package definition?

I haven't thought much about the aforementioned longstanding practice,
but that's not what I'm objecting to here.

Specifically, I'm objecting to the idea that the 'license' field need
only describe the files present in the build outputs.  For example, if a
hypothetical package is licensed under Expat but uses a build system
covered by the the Q Public License (QPL), I don't think we can omit
mention of the QPL just because those components are only used during
the build.

Does that make sense?

     Regards,
       Mark

-- 
Support Richard Stallman against the vicious disinformation campaign
against him and the FSF.  See <https://stallmansupport.org> for more.


  reply	other threads:[~2021-04-25 20:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25  6:15 Jam: which licence is this? Jack Hill
2021-04-25  7:16 ` Ricardo Wurmus
2021-04-25 17:25   ` Mark H Weaver
2021-04-25 17:35     ` Leo Famulari
2021-04-25 20:37       ` Mark H Weaver [this message]
2021-04-26 16:24         ` Leo Famulari
2021-05-02  4:53           ` Mark H Weaver
2021-05-02 15:20             ` Leo Famulari
2021-05-07 18:31               ` The purpose of the "license" list of a Guix package (Was: Re: Jam: which licence is this?) Chris Marusich
2021-05-07 19:23                 ` The purpose of the "license" list of a Guix package Chris Marusich
2021-05-08 10:16                 ` The purpose of the "license" list of a Guix package (Was: Re: Jam: which licence is this?) Leo Prikler
2021-05-08 11:17                   ` Ricardo Wurmus
2021-05-08 11:22                     ` Leo Prikler
2021-05-08 20:52                   ` Maxime Devos
2021-05-08 23:04                     ` Leo Prikler
2021-05-09  8:33                       ` Maxime Devos
2021-05-02 21:12             ` Jam: which licence is this? Ludovic Courtès
2021-04-25 17:42 ` Mark H Weaver
2021-04-28 13:20   ` Maxim Cournoyer
2021-04-25 20:23 ` Vagrant Cascadian
2021-04-25 20:49   ` Ricardo Wurmus
2021-04-25 20:53   ` Jack Hill
2021-04-25 21:04     ` Jack Hill
2021-04-26 14:36       ` Jack Hill
2021-05-02  5:02         ` Mark H Weaver
2021-04-25 21:41     ` Vagrant Cascadian

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=87h7juje1a.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).