all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Debugging info unavailability
Date: Wed, 03 May 2017 08:29:00 +0200	[thread overview]
Message-ID: <87bmrah2s3.fsf@elephly.net> (raw)
In-Reply-To: <87zieu7d8n.fsf@gmail.com>


Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

>>> Adding the "debug" to the default value of <package> would every package
>>> to now have a debug output; isn't this why Danny suggested to only
>>> change it at the build system level? That way nothing which doesn't have
>>> debugging symbols by default would break or have a useless debug output.
>>
>> Yes, it’s tempting to do it at the build-system level.  However, there
>> would now be a discrepancy between the actual outputs of the package
>> derivations and those of the package object: the package object would
>> declare just one output, but the corresponding derivation would have two
>> outputs.
>>
>
> Thanks for pointing that! It would be a Bad Thing indeed to introduce a
> mismatch between the package definition and the corresponding store
> item...
>
> Possibly another Bad Idea, but we could leave things as they are... And
> run a script which would rewrite (really, at the package definition
> level) the package outputs to include "debug" for every package built
> using the gnu/glib-or-gtk build systems? The commit will not be
> pretty, that would bring us where we want to be? Being Scheme, that'd be
> somewhat easy.

This sounds better.  I just don’t know if Hydra would have enough space
for all of these additional outputs.

Can we increase storage space on Hydra already or do we need to wait for
bayfront to replace the server in Boston?

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2017-05-03  6:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-23  0:02 Debugging info unavailability Danny Milosavljevic
2017-04-24  7:35 ` Tomas Cech
2017-05-02 10:08 ` Ludovic Courtès
2017-05-02 16:39   ` Maxim Cournoyer
2017-05-02 21:16     ` Ludovic Courtès
2017-05-03  4:53       ` Maxim Cournoyer
2017-05-03  6:29         ` Ricardo Wurmus [this message]
2017-05-03 10:11           ` Ludovic Courtès
2017-05-03 15:22             ` Maxim Cournoyer
2017-05-05 20:31               ` Ludovic Courtès
2017-05-05 21:47                 ` Ricardo Wurmus
2017-05-06 12:21                   ` Ludovic Courtès
2017-05-05 22:09                 ` Maxim Cournoyer
2017-05-06 12:26                   ` Distributing substitutes over GNUnet Ludovic Courtès
2017-05-11 15:05                     ` Maxim Cournoyer
2017-05-06 12:46                   ` Debugging info unavailability ng0
2017-05-11  5:13                     ` Maxim Cournoyer
2017-05-11 16:50                       ` ng0
2017-05-11 21:04                         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bmrah2s3.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.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 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.