From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: ‘snippet’ in <origin>
Date: Fri, 08 Nov 2013 22:15:14 +0100 [thread overview]
Message-ID: <878uwyvbml.fsf@gnu.org> (raw)
In-Reply-To: <87wqkjavxf.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 08 Nov 2013 14:02:20 +0100")
ludo@gnu.org (Ludovic Courtès) skribis:
> Now, I think we could replace ‘snippet’ by ‘phases’. That field would
> contain an <origin-phases> object with exactly 4 fields: unpack, patch,
> user (default to #f), and repack.
>
> In the LAPACK case, we’d do:
>
> (origin
> (uri ...)
> (sha256 ...)
> (phases (origin-phases (inherit %standard-origin-phases)
> (user '(for-each delete-file ...)))))
>
> I think that would address your problem. The set of phases would be
> fixed, though, unlike what ‘gnu-build-system’ does, but I think that’s
> fine.
The problem with that is that it makes the semantics less obvious: the
‘phases’ field is only used when it has a ‘user’ value other than #f, or
when the origin has a ‘patches’ field.
It seems that it needs more thought.
Ludo’.
next prev parent reply other threads:[~2013-11-08 21:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 9:08 LAPACK: tests fail; non-free files Nikita Karetnikov
2013-10-23 9:16 ` Nikita Karetnikov
2013-10-23 11:57 ` Andreas Enge
2013-10-24 19:33 ` Nikita Karetnikov
2013-11-04 19:19 ` [PATCH] gnu: Add LAPACK. (was: LAPACK: tests fail; non-free files) Nikita Karetnikov
2013-11-06 13:10 ` [PATCH] gnu: Add LAPACK Ludovic Courtès
2013-11-07 8:49 ` Nikita Karetnikov
2013-11-07 22:43 ` ‘snippet’ in <origin> Ludovic Courtès
2013-11-08 6:32 ` Mark H Weaver
2013-11-08 13:02 ` Ludovic Courtès
2013-11-08 15:13 ` Mark H Weaver
2013-11-08 21:15 ` Ludovic Courtès [this message]
2013-10-23 22:41 ` [PATCH] gnu: cmake: Bump to 2.8.12 Cyril Roelandt
2013-10-24 19:35 ` Nikita Karetnikov
2013-10-28 23:14 ` Ludovic Courtès
2013-10-29 8:22 ` Andreas Enge
2013-10-29 10:42 ` Ludovic Courtès
2013-10-31 22:42 ` Cyril Roelandt
2013-11-01 8:50 ` 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=878uwyvbml.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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 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.