unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: guix-devel@gnu.org
Subject: Re: Making local development easy
Date: Wed, 25 May 2016 17:48:55 +0200	[thread overview]
Message-ID: <5745C967.1030307@cbaines.net> (raw)
In-Reply-To: <87h9dmtukn.fsf@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 942 bytes --]

On 25/05/16 10:23, Alex Sassmannshausen wrote:
>> The first, is that the hash is required, which I only had to compute
>> once, but if I wanted to change the package, I would have to update
>> this, which is prohibitive to local development. As an improvement to
>> this, could the hash be optional, and if it does not exist, be
>> calculated when the build is performed?
> 
> From my perspective, I think silently calculating a hash on the fly if
> it is not provided would be problematic: it might lead to laziness in
> completing the hash, which would undermine the security model of Guix
> (if I understand correctly).
> 
> But maybe an explicit flag setting the declaration to "dev-mode", might
> be useful?

In the use case I described, where you are packaging a local resource, I
don't think this is relevant, as you implicitly trust your own machine.
If you don't for some reason, you can just specify the hash.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]

  reply	other threads:[~2016-05-25 15:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 18:25 Making local development easy Christopher Baines
2016-05-25  8:23 ` Alex Sassmannshausen
2016-05-25 15:48   ` Christopher Baines [this message]
2016-05-25 16:13   ` Leo Famulari
2016-05-25  9:29 ` Ricardo Wurmus
2016-05-25  9:34   ` Alex Sassmannshausen
2016-05-25 16:04   ` Christopher Baines
2016-05-25 18:33     ` Ricardo Wurmus
2016-05-26  8:07       ` Ludovic Courtès
2016-05-26 12:05         ` Thompson, David
2016-06-21  8:43           ` Ludovic Courtès
2016-05-25  9:36 ` Andy Wingo

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=5745C967.1030307@cbaines.net \
    --to=mail@cbaines.net \
    --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).