From: ludo@gnu.org (Ludovic Courtès)
To: Timothy Sample <samplet@ngyro.com>
Cc: 19973@debbugs.gnu.org
Subject: bug#19973: Grafts break debug outputs
Date: Thu, 23 Aug 2018 17:47:43 +0200 [thread overview]
Message-ID: <87zhxdkrts.fsf@gnu.org> (raw)
In-Reply-To: <87a7pea46g.fsf@ngyro.com> (Timothy Sample's message of "Wed, 22 Aug 2018 10:04:07 -0400")
Hello Timothy,
Timothy Sample <samplet@ngyro.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
[...]
>> Next we can fix build IDs similarly (see <https://bugs.gnu.org/25752>),
>> and maybe the Racket CRC issue that Timothy and Chris looked at
>> recently, and maybe the Java manifest issue as well (is it still
>> relevant?).
>
> The only concern I have is the level at which the hooks operate. In my
> draft patch¹ I had the hooks running both on the client side and the
> build side. This made it possible to get a bit more information about
> the derivation being grafted. If everything happens at the build level
> based on outputs, we will only be able to look at the structures and
> names of the outputs.
Yes, I agree that your proposal had the appeal of being possibly more
extensible that what I posted here. However, as I wrote there, there
are hooks that we’ll always want to run, independently of the input
packages, such as the .gnu_debuglink and build-ID hooks; also, it costs
nothing to have them unconditionally, we only pay for their
functionality when candidate files exist.
> That being said, this is probably okay. The Racket hook will just have
> to check for “share/racket” to determine if it runs (and fail safely if
> anything is amiss).
Yes, that should work well enough.
Thanks for your feedback!
Ludo’.
next prev parent reply other threads:[~2018-08-23 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 5:06 bug#19973: Grafts break debug outputs Mark H Weaver
2015-03-01 5:24 ` Mark H Weaver
2017-03-07 21:54 ` Ludovic Courtès
2017-03-10 13:14 ` Ludovic Courtès
2018-08-21 20:53 ` Ludovic Courtès
2018-08-21 20:56 ` bug#19973: [PATCH 1/2] grafts: Add high-level 'graft' procedure on the build side Ludovic Courtès
2018-08-21 20:56 ` bug#19973: [PATCH 2/2] grafts: Add (guix build debug-link) and use it Ludovic Courtès
2018-08-22 14:04 ` bug#19973: Grafts break debug outputs Timothy Sample
2018-08-23 15:47 ` Ludovic Courtès [this message]
2018-08-24 16:08 ` 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=87zhxdkrts.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=19973@debbugs.gnu.org \
--cc=samplet@ngyro.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).