From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Debugging Guix packages?
Date: Fri, 22 Jan 2016 05:13:02 +0100 [thread overview]
Message-ID: <20160122041302.GA7694@thebird.nl> (raw)
In-Reply-To: <8760ymy7nf.fsf@gnu.org>
On Thu, Jan 21, 2016 at 09:55:32PM +0100, Ludovic Courtès wrote:
> > I wonder how this could be implemented, any ideas?
>
> Roughly, we could generate a Scheme file containing the list of phases
> (the generated build script contains them, but it immediately passes
> them to ‘gnu-build’ or similar), which could be loaded into Guile. From
> there we could explicitly manipulate the list of phases and run them.
>
> There are complications though, such as the fact that build systems can
> lack the notion of phases altogether (this is the case of
> ‘trivial-build-system’, but it may be the only one.) I wonder if we
> should move phases from the build side to the host side at some point…
How about extending the -K switch with a build phase option where it
should stop?
I think the container thing is nice, but not really suitable for
fixing stuff (as Chris notes, it ends up read-only in the store). I am
pretty happy with -K.
Pj.
--
next prev parent reply other threads:[~2016-01-22 4:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 2:42 Debugging Guix packages? Jookia
2016-01-19 14:52 ` Ricardo Wurmus
2016-01-19 15:56 ` Christopher Allan Webber
2016-01-20 22:26 ` Ludovic Courtès
2016-01-21 0:21 ` Jookia
2016-01-21 1:27 ` Leo Famulari
2016-01-21 1:59 ` Ben Woodcroft
2016-01-21 20:55 ` Ludovic Courtès
2016-01-22 4:13 ` Pjotr Prins [this message]
2016-01-22 4:53 ` Jookia
2016-01-22 17:05 ` Ludovic Courtès
2016-01-21 20:58 ` Ludovic Courtès
2016-01-21 22:10 ` Jookia
2016-01-21 22:28 ` Christopher Allan Webber
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=20160122041302.GA7694@thebird.nl \
--to=pjotr.public12@thebird.nl \
--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).