all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org, Polchi <polchi.dabarov@riseup.net>
Subject: Re: Torrenting GuixSD!
Date: Wed, 25 Feb 2015 10:32:50 -0500	[thread overview]
Message-ID: <87oaoidn19.fsf@netris.org> (raw)
In-Reply-To: <20150225141215.GA5109@debian.math.u-bordeaux1.fr> (Andreas Enge's message of "Wed, 25 Feb 2015 15:12:15 +0100")

Andreas Enge <andreas@enge.fr> writes:

> On Wed, Feb 25, 2015 at 03:00:59PM +0100, Ludovic Courtès wrote:
>> Andreas Enge <andreas@enge.fr> skribis:
>> > I still think it would be nice to include the signature into the torrent.
>> It’s probably fine to point to the .sig that’s on alpha.gnu.org, no?
>
> Well, it is more a question of education than anything: By including the
> signature, downloaders are directly pointed to it. Of course, it can also
> be downloaded separately, but this is an additional step. We should make
> "the right thing" as easy as possible.

If we were to extend this argument to non-torrent downloads, then all
of our downloads (source tarballs and images) should be tar files
containing a signature bundled with the thing being signed.  mit-krb5
follows this policy with their source tarballs.  I suppose there can be
no arguments on matters of taste, but personally I don't like it.

I have some experience with torrents, and I tend to find it annoying
when downloads that would naturally be a single file are bundled into a
directory with other stuff.  For one thing, it means that I can't
organize my files as I prefer without keeping the directory name and
structure that the torrent creator chose, at least not if I want to
facilitate later seeding.

My preference would be to keep things as they are now.  IMO, it would be
better to educate people on how to download and check the detached
signature in our installation instructions.  That's a lesson that can be
used for almost every software package that is signed upstream, which
would be far more useful than educating them on some non-standard
signature distribution method that hardly anyone uses.

    Regards,
      Mark

  reply	other threads:[~2015-02-25 15:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 17:23 Torrenting GuixSD! Polchi
2015-02-13 22:53 ` David Thompson
2015-02-14  2:50   ` Eric Bavier
2015-02-23 20:47     ` Ludovic Courtès
2015-02-23 20:54       ` Andreas Enge
2015-02-25 14:00         ` Ludovic Courtès
2015-02-25 14:12           ` Andreas Enge
2015-02-25 15:32             ` Mark H Weaver [this message]
2015-02-25 17:51               ` Andreas Enge
2015-02-25 21:47                 ` Ludovic Courtès
2015-02-25 21:51                   ` Andreas Enge
2015-02-14  9:30 ` Andreas Enge

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=87oaoidn19.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=polchi.dabarov@riseup.net \
    /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.