unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Tomáš Čech" <sleep_walker@gnu.org>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: ‘guix publish’ now compresses archives
Date: Wed, 20 Jul 2016 18:10:29 +0200	[thread overview]
Message-ID: <20160720161029.fs5ee723ro3vfpvi@venom> (raw)
In-Reply-To: <CAJ=RwfZM6bWF5NevWA3TgqxUKJVFog_UixBqE4Nu3qPjhE+4QQ@mail.gmail.com>

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

On Wed, Jul 20, 2016 at 09:12:53AM -0400, Thompson, David wrote:
>On Wed, Jul 20, 2016 at 9:05 AM, Tomáš Čech <sleep_walker@gnu.org> wrote:
>
>> First, I'm not saying that we should do that for every archive, but I
>> think that having a way how to automatically export this information
>> would be great and I see it as a week point for using Guix packages as
>> alternative to Snappy or Flatpak.
>
>I don't really understand the point of this back-and-forth.  It's
>quite simple: If the user builds the same package expression with the
>same version of Guix, they will get the same result if the build is
>deterministic.

Yes.

>I don't understand the contrast with Snappy and Flatpak because they
>don't provide this feature at all, opting instead to provide opaque
>binaries with no real provenance.

Snappy and Flatpak does not provide this feature but Guix could.

>I can only assume that there is some fundamental misunderstanding
>about Guix going on here.

I don't think so. My guess is that you're using Guix too much as OS
and too little as package manager in another OS.

Nevermind, enough of this. It seems that noone is interested in that
anyway.

S_W

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-07-20 16:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18 22:22 ‘guix publish’ now compresses archives Ludovic Courtès
2016-07-19  6:29 ` Tomáš Čech
2016-07-19 10:03   ` Pjotr Prins
2016-07-19 13:15   ` Ludovic Courtès
2016-07-19 13:42     ` Tomáš Čech
2016-07-19 14:23       ` Ricardo Wurmus
2016-07-19 15:50         ` Tomáš Čech
2016-07-20 11:20           ` Ricardo Wurmus
2016-07-20 13:05             ` Tomáš Čech
2016-07-20 13:12               ` Thompson, David
2016-07-20 16:10                 ` Tomáš Čech [this message]
2016-07-21  5:33                 ` Ricardo Wurmus
2016-07-21 15:58                   ` Thompson, David
2016-07-21  5:53               ` Ricardo Wurmus
2016-07-21 20:50                 ` Tomáš Čech
2016-07-21 10:12 ` Andy Wingo
2016-07-21 12:43   ` Ludovic Courtès

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=20160720161029.fs5ee723ro3vfpvi@venom \
    --to=sleep_walker@gnu.org \
    --cc=dthompson2@worcester.edu \
    --cc=guix-devel@gnu.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).