all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: david larsson <david.larsson@selfhosted.xyz>
Cc: Parnikkapore <poomklao@yahoo.com>,
	 help-guix@gnu.org,
	help-guix-bounces+someone=selfhosted.xyz@gnu.org
Subject: Re: Can Guix channels be non-GPL?
Date: Thu, 15 Jun 2023 09:45:05 -0400	[thread overview]
Message-ID: <87legkvnz2.fsf@gmail.com> (raw)
In-Reply-To: <abb46d148d780066478f5a122d7642be@selfhosted.xyz> (david larsson's message of "Wed, 14 Jun 2023 21:51:10 +0200")

Hi David,

david larsson <david.larsson@selfhosted.xyz> writes:

> On 2023-06-12 14:13, Parnikkapore wrote:
>> Hi Guix!
>> I realized a while ago that, since pretty much all Guix channels
>> have
>> to import some module from Guix (e.g. (guix packages)), it's basically
>> impossible for a Guix channel to have any license other than GPLv3 or
>> GPLv3+.
>> Is this correct? If this is true, I'll have to relicense my channel
>> accordingly. (it's currently under LGPL since that's my preference)

I believe that's correct.  If your channel is public/distributed to
someone, it ought to be GPLv3+.

-- 
Thanks,
Maxim


  reply	other threads:[~2023-06-15 13:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <793f8796901ec5477972c805557bd66267af3310.camel.ref@yahoo.com>
2023-06-12 12:13 ` Can Guix channels be non-GPL? Parnikkapore
2023-06-13 10:35   ` pelzflorian (Florian Pelz)
2023-06-13 13:56     ` Saku Laesvuori
2023-06-13 15:45       ` Dr. Arne Babenhauserheide
2023-06-13 16:08       ` pelzflorian (Florian Pelz)
2023-06-13 18:39         ` pelzflorian (Florian Pelz)
2023-06-13 18:52           ` Dr. Arne Babenhauserheide
2023-06-14  7:08   ` pelzflorian (Florian Pelz)
2023-06-14 19:51   ` david larsson
2023-06-15 13:45     ` Maxim Cournoyer [this message]
2023-06-16 15:09       ` Parnikkapore

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=87legkvnz2.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=david.larsson@selfhosted.xyz \
    --cc=help-guix-bounces+someone=selfhosted.xyz@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=poomklao@yahoo.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.