all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: elaexuotee@wilsonb.com
Cc: 47905@debbugs.gnu.org
Subject: [bug#47905] gnu: Add rasdaemon.
Date: Tue, 20 Apr 2021 12:08:48 -0400	[thread overview]
Message-ID: <YH78kCXuaZNRZBUI@jasmine.lan> (raw)
In-Reply-To: <3R38A8AKFTHYA.2KFNX2D2XIN4U@wilsonb.com>

On Tue, Apr 20, 2021 at 02:54:49PM +0900, elaexuotee@wilsonb.com wrote:
> The `FSF All Permissive License' just comes from the INSTALL file.  In general,
> I'm aware that we can include multiple licenses, so the above output would look
> like:
> 
>     (license `(,license:fsf-free ,license:lgpl2.1 ,license:gpl2 ,license:gpl2+))
> 
> However, legally-speaking, was is the correct approach here?

Overall, the program is distributed under the GPL version 2, based on
COPYING (whether or not "later versions" are allowed depends on license
headers of individual files).

Some components may have other licenses, but I'd say the whole thing —
the "program" as we use it — is GPL 2.

In general, we redistribute the program under a single license, so that
is what the license field should say.  Maybe if there is some really
valuable component that can be used under a different license, we can
add a code comment about it.  But, I don't think it's helpful to list
the licenses of files such as INSTALL, nor is it unusual that they have
a different license than the whole.

I would refer to this page for more advice about the GPL:

https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility

I'm not a legal expert, and my understanding is that none of this stuff
is really "settled" or "well understood" legally — that would require
extensive and repeated litigation, at least in the USA, which has not
occurred.




  reply	other threads:[~2021-04-20 16:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20  4:24 [bug#47905] gnu: Add rasdaemon elaexuotee--- via Guix-patches via
2021-04-20  5:04 ` Leo Famulari
2021-04-20  5:07 ` Leo Famulari
2021-04-20  5:54   ` elaexuotee--- via Guix-patches via
2021-04-20 16:08     ` Leo Famulari [this message]
2021-04-20  5:30 ` Leo Famulari
2021-04-20  6:18   ` elaexuotee--- via Guix-patches via
2021-04-20 16:19     ` Leo Famulari
2021-04-20  5:33 ` Leo Famulari
2021-04-20  6:23   ` elaexuotee--- via Guix-patches via
2021-04-20 16:20     ` Leo Famulari
2021-04-20  7:10   ` elaexuotee--- via Guix-patches via
2021-04-20 16:23     ` Leo Famulari
2021-04-22 10:01       ` elaexuotee--- via Guix-patches via
2021-04-24 16:33         ` bug#47905: " Leo Famulari

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=YH78kCXuaZNRZBUI@jasmine.lan \
    --to=leo@famulari.name \
    --cc=47905@debbugs.gnu.org \
    --cc=elaexuotee@wilsonb.com \
    /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.