From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: Olivier Dion via <help-guix@gnu.org>
Subject: Re: Questions regarding substitutes with debug output
Date: Sat, 23 Apr 2022 23:38:57 -0400 [thread overview]
Message-ID: <87pml72lri.fsf@gmail.com> (raw)
In-Reply-To: <87ee1pur82.fsf@laura> (Olivier Dion's message of "Fri, 22 Apr 2022 10:29:01 -0400")
Hello,
Olivier Dion <olivier.dion@polymtl.ca> writes:
> On Fri, 22 Apr 2022, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>>> I require debugging symbols of multiple packages. Some of them
>>> already have a debug output from the main guix channel, but others
>>> don't. So I had in mind to make a channel and publish the
>>> substitutes with the debug outputs.
>>
>> In general, if you need debug symbols for something, I think it's OK
>> to contribute adding them to Guix proper (in a debug output), unless
>> they make like >= 1 GiB (as I can imagine may be the case for IceCat).
>
> Okay I will try. I'm not sure how easy it is so add debug symbols to some
> packages e.g. git, nginx. In any case I need them, so I will contribute
> back to the main channel if it works.
When the package uses the gnu-build-system, it is usually just adding a
"debug" outputs and the copying of the stripped symbols to this output
is taken care of automatically. Some packages use their own flags or a
release build without symbols in which case just adding "debug" alone
won't be enough.
>>> How could I make sure that Guix use my version of Firefox over the one
>>> defined by the main channel? My guess is to change the name of my
>>> package to something like "my-firefox". But it would be nicer if I
>>> don't have to do so. Perhaps there's a way to force channel
>>> preference?
>>
>> Channels can only extend, not override the default Guix channel (the
>> world would be a bit of a mess if it did). So the easiest path is to
>> use a different name; alternatively for graph rewriting you could use
>> the various APIs to effect package transformations.
>
> Would be nice to have some way to specify channel in a package
> specification. I don't think that it would break things if we
> considerer channels as namespaces, i.e. different graph. A
> specification like:
>
> {channel}package@version:output
>
> would be useful. For now I will just rename them to "my/package".
That could be neat, yes. I wonder how easy/difficult its implementation
would be.
Thanks,
Maxim
next prev parent reply other threads:[~2022-04-24 3:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 17:32 Questions regarding substitutes with debug output Olivier Dion via
2022-04-22 4:22 ` Maxim Cournoyer
2022-04-22 14:29 ` Olivier Dion via
2022-04-24 3:38 ` Maxim Cournoyer [this message]
2022-04-24 14:56 ` Olivier Dion via
2022-04-25 4:10 ` Maxim Cournoyer
2022-04-28 8:13 ` zimoun
2022-04-28 8:58 ` Ricardo Wurmus
2022-04-28 14:11 ` Olivier Dion via
2022-04-28 14:18 ` Ricardo Wurmus
2022-04-28 14:25 ` Olivier Dion via
2022-04-29 5:06 ` Ricardo Wurmus
2022-04-28 14:20 ` Olivier Dion via
2022-04-29 8:49 ` zimoun
2022-04-29 14:47 ` Olivier Dion via
2022-04-29 16:01 ` Ricardo Wurmus
2022-04-29 16:17 ` Olivier Dion via
2022-04-29 20:08 ` Ricardo Wurmus
2022-04-29 20:53 ` Olivier Dion via
2022-05-09 10:33 ` zimoun
2022-05-09 13:33 ` Ricardo Wurmus
2022-05-09 14:37 ` zimoun
2022-04-29 16:06 ` zimoun
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=87pml72lri.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=help-guix@gnu.org \
--cc=olivier.dion@polymtl.ca \
/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.