unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Adrien 'neox' Bourmault <neox@gnu.org>, help-guix@gnu.org
Subject: Re: License compliance when redistributing images built with 'guix system'.
Date: Sun, 28 Jul 2024 19:20:36 +0200	[thread overview]
Message-ID: <20240728192036.7bc5525a@primary_laptop> (raw)
In-Reply-To: <874j8oexq9.fsf@gmail.com>

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

On Wed, 17 Jul 2024 19:26:22 +0200
Simon Tournier <zimon.toutoune@gmail.com> wrote:

> Hi Denis,
Hi,

> Well, I do not see any reply to this message.  So even very late. :-)
Thanks a lot.

> > But for redistributing complete images built with guix system image,
> > like a VM image for instance, I'm unsure how to do it and I was
> > wondering if there is a standard way to do that.
> 
> Well, I am not sure to get if you speak about the source or about the
> binary of this image?
The use case is that if I distribute a bootable system image made with
Guix (like a VM image for instance), I'd like an easy way of complying
with all the free software licenses to avoid any legal risks.

Since the image contains many binaries I guess an easy way to comply with
licenses like the GPLv2 could be to provide like a tarball with inside
all the source code corresponding to the binaries inside the VM image.
If there is also extra source code (compilers, etc) it's probably not a
big issue.

As I understand it's easier for distributions like Guix or even more
classical distributions to comply because they typically provide source
code, packages and images from the same servers.

But as a user I'd like to avoid building everything myself, and I'd
like to redistribute some images I make without any legal risks.

> From your configuration file, you could extract the manifest file
> which includes all the packages and based on that you could apply some
> “sources=transitive” options.
Thanks. I think this could be a good option.

Denis.

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

  reply	other threads:[~2024-07-28 17:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23  0:09 License compliance when redistributing images built with 'guix system' Denis 'GNUtoo' Carikli
2024-07-17 17:26 ` Simon Tournier
2024-07-28 17:20   ` Denis 'GNUtoo' Carikli [this message]
2024-09-30 20:11   ` Denis 'GNUtoo' Carikli
2024-11-18  8:41     ` Denis 'GNUtoo' Carikli
2024-11-18 12:38       ` Denis 'GNUtoo' Carikli

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=20240728192036.7bc5525a@primary_laptop \
    --to=gnutoo@cyberdimension.org \
    --cc=help-guix@gnu.org \
    --cc=neox@gnu.org \
    --cc=zimon.toutoune@gmail.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.
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).