all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: guix-devel@gnu.org, raid5atemyhomework@protonmail.com,
	Domagoj Stolfa <ds815@gmx.com>
Subject: Re: ZFS part of Guix? RFC?
Date: Fri, 26 Nov 2021 16:28:04 +0100	[thread overview]
Message-ID: <20211126162804.726829e3@primarylaptop.localdomain> (raw)
In-Reply-To: <878rxd5nlo.fsf@ponder>

[-- Attachment #1: Type: text/plain, Size: 2738 bytes --]

On Wed, 24 Nov 2021 12:02:11 -0800
Vagrant Cascadian <vagrant@debian.org> wrote:

> On 2021-11-24, Denis 'GNUtoo' Carikli wrote:
> > On Wed, 24 Nov 2021 13:03:18 +0100
> > "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:
> >
> >> On Wed, Nov 24, 2021 at 01:45:19AM +0100, Denis 'GNUtoo' Carikli
> >> wrote:
> 
> https://sfconservancy.org/blog/2016/feb/25/zfs-and-linux/
> 
> > That article states that:
> >> Pure distribution of source with no binaries is undeniably
> >> different. When distributing source code and no binaries,
> >> requirements in those sections of GPLv2 and CDDLv1 that cover
> >> modification and/or binary (or “Executable”, as CDDLv1 calls it)
> >> distribution do not activate. Therefore, the analysis is simpler, 
> > So is it legal because zfs-on-linux is distributed as source and
> > that the CDDL license incompatible requirements are waived when it
> > is distributed as source?
> 
> Rather than "waived", they are simply not applicable. There is
> basically an "if" statement in the CDDL that triggers the
> incompatibility, and in the case of source-only distribution, the
> conflicting parts of the licenses do not come into play.

I've not checked that in details yet but for now I'll assume that this
holds (until proven otherwise).

While thinking about this very weird case of combining GPL and CDDL
code together, I wonder if the fact that we can't redistribute binaries
still makes it free software.

At least the free software definition doesn't have anything that cover
this specific case:
> The freedom to run the program as you wish, for any purpose
> (freedom 0).

> The freedom to study how the program works, and change it so it
> does your computing as you wish (freedom 1). Access to the source
> code is a precondition for this.

> The freedom to redistribute copies so you can help your neighbor
> (freedom 2).

> The freedom to distribute copies of your modified versions to others
> (freedom 3). By doing this you can give the whole community a chance
> to benefit from your changes. Access to the source code is a
> precondition for this.

But I wonder if a license that forbid binary redistribution would still
be considered free or not. 

And also conditions may apply to the specific case, for instance here
nobody has an alternative (including Oracle) for redistributing
binaries unless Oracle releases ZFS under a license fully compatible
with the GPL or that Linux is re-licensed (that would probably be more
complicated than rewriting ZFS from scratch).

Other cases like a vendor forbidding binary distribution to make its
users pay for nonfree licenses might be way more problematic.

Denis.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-11-26 15:28 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 19:33 Effectively force all GNOME users to locally compile ZFS? Mark H Weaver
2021-07-03 19:53 ` Tobias Geerinckx-Rice
2021-07-05  9:53   ` Ludovic Courtès
2021-07-05 17:48     ` Mark H Weaver
2021-07-07 11:59       ` Tobias Geerinckx-Rice
2021-07-11 20:07         ` Mark H Weaver
2021-07-07 11:34     ` Tobias Geerinckx-Rice
2021-07-03 20:01 ` Maxime Devos
2021-07-03 20:16   ` Tobias Geerinckx-Rice
2021-07-03 20:46     ` Domagoj Stolfa
2021-07-03 21:38       ` Tobias Geerinckx-Rice
2021-07-03 21:53         ` Tobias Geerinckx-Rice
2021-11-20  1:09       ` Denis 'GNUtoo' Carikli
2021-11-20  2:34         ` Tobias Geerinckx-Rice
2021-11-21  1:33           ` Denis 'GNUtoo' Carikli
2021-11-21 10:54             ` ZFS part of Guix? RFC? (Re: Effectively force all GNOME users to locally compile ZFS?) pelzflorian (Florian Pelz)
2021-11-22 16:50               ` Denis 'GNUtoo' Carikli
2021-11-22 18:10               ` pelzflorian (Florian Pelz)
2021-11-23 16:37                 ` Denis 'GNUtoo' Carikli
2021-11-23 17:29                 ` Ludovic Courtès
2021-11-23 23:50                   ` Denis 'GNUtoo' Carikli
2021-11-24  0:45                     ` Denis 'GNUtoo' Carikli
2021-11-24 12:03                       ` pelzflorian (Florian Pelz)
2021-11-24 12:32                         ` pelzflorian (Florian Pelz)
2021-11-24 12:51                           ` zimoun
2021-11-24 14:40                             ` pelzflorian (Florian Pelz)
2021-11-24 20:25                               ` zimoun
2021-11-24 13:33                         ` Denis 'GNUtoo' Carikli
2021-11-24 20:02                           ` ZFS part of Guix? RFC? Vagrant Cascadian
2021-11-26 15:28                             ` Denis 'GNUtoo' Carikli [this message]
2021-11-26 20:02                               ` Denis 'GNUtoo' Carikli
2021-11-26 20:34                                 ` Vagrant Cascadian
2021-11-27 15:19                                   ` Denis 'GNUtoo' Carikli
2021-11-30 15:22                               ` raid5atemyhomework
2021-11-30 21:22                                 ` Denis 'GNUtoo' Carikli
2021-11-24  1:24                     ` ZFS part of Guix? RFC? (Re: Effectively force all GNOME users to locally compile ZFS?) zimoun
2021-11-24 17:24                 ` Leo Famulari
2021-11-21 22:18             ` Effectively force all GNOME users to locally compile ZFS? zimoun
2021-07-04 20:11     ` Mark H Weaver
2021-07-05 10:21       ` Giovanni Biscuolo
2021-07-05 17:59         ` Mark H Weaver
2021-07-07 12:20       ` Tobias Geerinckx-Rice

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=20211126162804.726829e3@primarylaptop.localdomain \
    --to=gnutoo@cyberdimension.org \
    --cc=ds815@gmx.com \
    --cc=guix-devel@gnu.org \
    --cc=raid5atemyhomework@protonmail.com \
    --cc=vagrant@debian.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.