unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: "Thompson, David" <dthompson2@worcester.edu>,
	Raghav Gururajan <raghavgururajan@disroot.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix and FSDG
Date: Sat, 23 Nov 2019 11:04:24 +0100	[thread overview]
Message-ID: <87a78mkixj.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <CAJ=RwfaLQx=ekQAZeW8rkeFtRhLbUKivBuvB=+QzPtqngi9q=A@mail.gmail.com>

Hello,

"Thompson, David" <dthompson2@worcester.edu> writes:

[...]

> This exact
> circumstance was brought up in the early days of the Guix project when
> FSDG compliance was a big topic of discussion because Ludovic and RMS
> were making sure that Guix conformed to it.  It is true that Guix will
> download source archives for packages that *may* contain files with a
> nonfree license.  However, Guix has a special mechanism developed
> specifically to deal with this issue.  In Guix, the <origin> data type
> is used to store information about a package's source code.  In this
> data structure there is a field called "snippet" which may contain a
> custom procedure written by the person that wrote the package.  The
> role of the snippet procedure is to *remove* any files in the source
> archive that are not freely licensed.  The result is a new source
> archive that contains only freely licensed files.  The most important
> part of this process is that the original source archive is *never*
> accessible to the Guix user via any Guix tools.  The original archive
> is discarded and does not end up in the canonical location for Guix
> data: /gnu/store.  Thus, running `guix build --source
> problematic-package` will only ever return the cleaned archive, never
> the original with nonfree files.  Therefore, Guix has taken sufficient
> technical measures to avoid steering its user towards nonfree software
> and thus Guix is compliant with the FSDG.

[...]

can we please consider to add a specific section to the manual including
a properly redacted copy of this exact text?

I think that specifically stating that no non-free code will be saved in
store due to ``guix build`` is specifically addressed by the snippet
field in <origin> (other procedures?) *and* assessed [1] by guix
maintainers will be of great help in all future discussions on this
topic (and there will be other discussions :-) )

WDYT?

David whould you like to propose a patch if anouth consensus on this
topic is reached? If you cannot, I can help on this.


Thanks! Gio'



[1] it means that missing to remove non-free code is considered a bug
and treated accordingly to the FSGD

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

      parent reply	other threads:[~2019-11-23 10:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 10:02 Guix and FSDG Raghav Gururajan
2019-11-22 14:59 ` ng0
2019-11-22 15:26   ` ng0
2019-11-22 17:03 ` Thompson, David
2019-11-22 19:20   ` Raghav Gururajan
2019-11-22 20:26     ` Thompson, David
2019-11-23  1:22   ` Clément Lassieur
2019-11-23 10:27     ` Giovanni Biscuolo
2019-11-23 10:54       ` Clément Lassieur
2019-11-23 17:59         ` Ludovic Courtès
2019-11-25 21:39           ` zimoun
2019-11-26  8:33         ` Giovanni Biscuolo
2019-11-23 10:04   ` Giovanni Biscuolo [this message]

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=87a78mkixj.fsf@roquette.mug.biscuolo.net \
    --to=g@xelera.eu \
    --cc=dthompson2@worcester.edu \
    --cc=guix-devel@gnu.org \
    --cc=raghavgururajan@disroot.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 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).