unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Troy Sankey <sankeytms@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] doc: clarification for hashing git checkouts
Date: Mon, 11 Jul 2016 12:17:31 -0400	[thread overview]
Message-ID: <20160711161731.GB7615@jasmine> (raw)
In-Reply-To: <20160711053340.15418.55286@what>

On Mon, Jul 11, 2016 at 01:33:40AM -0400, Troy Sankey wrote:
> Hashing sources is becoming quite compilated!  I can't wait until 'guix
> download' supports git, then this could be automated.

In that case, `guix download` would need to take a Git hash as an
argument.

In general, I think it's a good idea to avoid `guix download` when
writing packages, unless you make sure to double-check that the
package's origin field works as expected. I've submitted packages with a
bad URL that was masked because the tarball was already in my store from
`guix download`. So, now I always download my sources "by hand" and
calculate the hash from the result of that.

  parent reply	other threads:[~2016-07-11 16:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-10 21:54 [PATCH] doc: clarification for hashing git checkouts Troy Sankey
2016-07-10 23:16 ` Leo Famulari
2016-07-11  0:13   ` Pjotr Prins
2016-07-11  5:33     ` Troy Sankey
2016-07-11 15:36       ` Pjotr Prins
2016-07-11 16:17       ` Leo Famulari [this message]
2016-07-11  5:18   ` Troy Sankey
2016-07-11 16:35     ` ng0
2016-07-11 17:50       ` Troy Sankey
2016-07-13 22:04         ` 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=20160711161731.GB7615@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=sankeytms@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.
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).