From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Graft hooks
Date: Fri, 24 Aug 2018 17:59:23 -0400 [thread overview]
Message-ID: <87va7zbf44.fsf@netris.org> (raw)
In-Reply-To: <87d0u8qda6.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 24 Aug 2018 12:17:37 +0200")
Hi Ludovic,
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> I think it would be quite unfortunate if _every_ graft had to run
>> _every_ graft hook, or if every graft hook had to be defined in
>> (guix grafts) and/or (guix build graft).
>>
>> It's reasonable to have a few global graft hooks, e.g. for handling
>> debugging information, but I would greatly prefer for Guix to also have
>> a mechanism allowing individual packages or build systems to introduce
>> graft hooks without modifying (guix grafts) or (guix build graft), and
>> for such a mechanism to be used for Racket and its libraries.
>
> Sure, like I wrote, a more extensible solution along the lines of what
> Timothy and you suggest sounds better long-term. It just happens to be
> harder to implement today (in particular until ‘wip-build-systems-gexp’
> is merged), and not entirely clear how this could work, as discussed
> with Timothy.
That's fine. This solution is fine for now, as long as the number of
graft hooks is fairly small. Maybe we can revisit this after
'wip-build-systems-gexp' is merged.
Thanks,
Mark
prev parent reply other threads:[~2018-08-24 22:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-12 19:49 Graft hooks Timothy Sample
2018-08-13 0:28 ` Christopher Lemmer Webber
2018-08-13 7:19 ` Gábor Boskovits
2018-08-20 9:12 ` Ludovic Courtès
2018-08-21 15:42 ` Timothy Sample
2018-08-22 14:21 ` Ludovic Courtès
2018-08-22 18:29 ` Timothy Sample
2018-08-24 10:09 ` Ludovic Courtès
2018-08-22 19:15 ` Christopher Lemmer Webber
2018-08-23 7:15 ` Mark H Weaver
2018-08-23 9:54 ` Gábor Boskovits
2018-08-24 10:17 ` Ludovic Courtès
2018-08-24 21:59 ` Mark H Weaver [this message]
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=87va7zbf44.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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).