unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: clement@lassieur.org (Clément Lassieur)
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>,
	Raghav Gururajan <raghavgururajan@disroot.org>
Subject: Re: Guix and FSDG
Date: Sat, 23 Nov 2019 02:22:31 +0100	[thread overview]
Message-ID: <877e3rz8rs.fsf@lassieur.org> (raw)
In-Reply-To: <CAJ=RwfaLQx=ekQAZeW8rkeFtRhLbUKivBuvB=+QzPtqngi9q=A@mail.gmail.com> (David Thompson's message of "Fri, 22 Nov 2019 12:03:36 -0500")

Hi David,

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

> I believe this is incorrect and I will explain why.  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.

Unfortunately I think this isn't true.  For example this is what 'guix
build -S zpaq' outputs:

--8<---------------cut here---------------start------------->8---
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
The following derivation will be built:
   /gnu/store/k9g90yqfcz8c0lnz1mcfd9k53llyw8wh-zpaq715.tar.xz.drv
2,7 MB will be downloaded:
   /gnu/store/32xxhz1sf3v9wxkhlvf4b9493dy588gi-zpaq715.zip
substituting /gnu/store/32xxhz1sf3v9wxkhlvf4b9493dy588gi-zpaq715.zip...
downloading from https://ci.guix.gnu.org/nar/32xxhz1sf3v9wxkhlvf4b9493dy588gi-zpaq715.zip...
 zpaq715.zip  2.6MiB                  2.4MiB/s 00:01 [##################] 100.0%

building /gnu/store/k9g90yqfcz8c0lnz1mcfd9k53llyw8wh-zpaq715.tar.xz.drv...
/gnu/store/cnqpra8vr2l5fz00rr4yj4bp3hr00cfw-tar-1.32/bin/tar: Option --mtime: Treating date '@0' as 1970-01-01 00:00:00
zpaq715.zip/
zpaq715.zip/COPYING
zpaq715.zip/Makefile
zpaq715.zip/libzpaq.cpp
zpaq715.zip/libzpaq.h
zpaq715.zip/readme.txt
zpaq715.zip/zpaq.cpp
zpaq715.zip/zpaq.pod
source is under 'zpaq715.zip'
`/gnu/store/32xxhz1sf3v9wxkhlvf4b9493dy588gi-zpaq715.zip/libzpaq.h' -> `zpaq715.zip/libzpaq.h'
`/gnu/store/32xxhz1sf3v9wxkhlvf4b9493dy588gi-zpaq715.zip/zpaq.pod' -> `zpaq715.zip/zpaq.pod'
`/gnu/store/32xxhz1sf3v9wxkhlvf4b9493dy588gi-zpaq715.zip/Makefile' -> `zpaq715.zip/Makefile'
`/gnu/store/32xxhz1sf3v9wxkhlvf4b9493dy588gi-zpaq715.zip/zpaq.exe' -> `zpaq715.zip/zpaq.exe'
`/gnu/store/32xxhz1sf3v9wxkhlvf4b9493dy588gi-zpaq715.zip/libzpaq.cpp' -> `zpaq715.zip/libzpaq.cpp'
`/gnu/store/32xxhz1sf3v9wxkhlvf4b9493dy588gi-zpaq715.zip/COPYING' -> `zpaq715.zip/COPYING'
`/gnu/store/32xxhz1sf3v9wxkhlvf4b9493dy588gi-zpaq715.zip/zpaq.cpp' -> `zpaq715.zip/zpaq.cpp'
`/gnu/store/32xxhz1sf3v9wxkhlvf4b9493dy588gi-zpaq715.zip/zpaq64.exe' -> `zpaq715.zip/zpaq64.exe'
`/gnu/store/32xxhz1sf3v9wxkhlvf4b9493dy588gi-zpaq715.zip/readme.txt' -> `zpaq715.zip/readme.txt'
successfully built /gnu/store/k9g90yqfcz8c0lnz1mcfd9k53llyw8wh-zpaq715.tar.xz.drv
/gnu/store/ran43jk8ngc60zzxgzhzdhkrpyb9i0ji-zpaq715.tar.xz
--8<---------------cut here---------------end--------------->8---

Both /gnu/store/32xxhz1sf3v9wxkhlvf4b9493dy588gi-zpaq715.zip and
/gnu/store/ran43jk8ngc60zzxgzhzdhkrpyb9i0ji-zpaq715.tar.xz are
accessible.

The former allows me to access zpaq64.exe and zpaq.exe although the
snippet is:

--8<---------------cut here---------------start------------->8---
(snippet
 ;; Delete irrelevant pre-compiled binaries.
 '(begin
    (for-each delete-file (find-files "." "\\.exe$"))
    #t))
--8<---------------cut here---------------end--------------->8---

Clément

  parent reply	other threads:[~2019-11-23  1:22 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 [this message]
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

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=877e3rz8rs.fsf@lassieur.org \
    --to=clement@lassieur.org \
    --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).