From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org, Guix-devel <guix-devel-bounces+me=tobias.gr@gnu.org>
Subject: Re: Debugging and source code
Date: Thu, 26 Jan 2017 09:58:38 +0100 [thread overview]
Message-ID: <0df93cbe49d6e05ddd59285db168d9da@tobias.gr> (raw)
In-Reply-To: <87wpdiz1eg.fsf@gmail.com>
On 2017-01-26 09:11, Chris Marusich wrote:
> We have "guix build -S foo" which fetches the source. It sounds like
> you're suggesting that we remove this and replace it with a "source"
> (or
> "debug-full") output for each package, so to get the source you would
> run "guix build foo:source" instead. Is my understanding correct?
Interesting idea (:source, not :debug-full)! Two minor points:
Won't that mean that the package has to be built to completion at least
once, somewhere, to output its own :source? If so, adding special-case
code to avoid that would not be a net win.
We'd also have to choose between keeping a misleading name, 'outputs',
and a global bike-sed.
Kind regards,
T G-R
--
Sent from a web browser. Excuse/enjoy my brevity.
next prev parent reply other threads:[~2017-01-26 8:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 6:53 Debugging and source code Pjotr Prins
2017-01-25 13:22 ` Ludovic Courtès
2017-01-25 13:26 ` Pjotr Prins
2017-01-25 17:54 ` Ludovic Courtès
2017-01-26 3:58 ` Pjotr Prins
2017-01-26 8:11 ` Chris Marusich
2017-01-26 8:43 ` Pjotr Prins
2017-01-26 8:58 ` Tobias Geerinckx-Rice [this message]
2017-01-26 18:03 ` Ludovic Courtès
2017-01-26 9:54 ` Ludovic Courtès
2017-01-28 4:57 ` Pjotr Prins
2017-01-30 9:05 ` Ludovic Courtès
2017-01-30 10:08 ` Danny Milosavljevic
2017-01-25 20:41 ` Danny Milosavljevic
2017-01-26 4:03 ` Pjotr Prins
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=0df93cbe49d6e05ddd59285db168d9da@tobias.gr \
--to=me@tobias.gr \
--cc=guix-devel-bounces+me=tobias.gr@gnu.org \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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).