IRC channel logs

<nckx>goggles-bot: Welcome snack.

<podiki>nckx: people snack.

<podiki>err...snack for a person, not of a person

<nckx>SoylentSnax®

<podiki>jeez what has sneek been snacking on this whole time??

<nckx>People who say 'open-source Linux'.

<nckx>Since the bot wasn't logging, there are no logs. I sometimes fill in the gaps with my own logs. I'll do so if I don't forget.

<sepeth>Hi Guix, I get Unbound variable: target-aarch64? for a gexp in a package definition. Do I need to import something for this? This is roughly what I am doing: (arguments (list #:phases #~(modify-phases ... (if (target-aarch64?) "-arm" "") ...)

<sepeth>Hmm, guix utils.

<nckx>#$(if (target-aarch64?) …)

<nckx>‘I seem to need to import (guix utils)’ really means ‘I used something meant to be used the host side on the build side’.

<sepeth>Oh I see, thanks, it worked ^-^

<nckx>Yay! I was about to add that you could also use (if #$(target-aarch64?) …) if you really need to keep the rest gexped.

<nckx>But I prefer the former style if it works.

<sepeth>Beautiful ^-^

<jmes>When defining a service-type and using the define-configuration macro, how do I specify that a configuration record field could be more than 1 type?

<jmes>I guess I just define my own type for that.

<jmes>But for my use case I can use define-maybe to achieve what I need

<meaty>what's the way to skip the 'check' phase in a package definition?

<nckx>(arguments … #:tests? #f …)

<nckx>On the CLI side, there is --without-tests=PACKAGE.

<nckx>This will do the same thing, and hence change the output hash, so you're not only building PACKAGE locally but also any dependents.

<meaty>this worked thanks!

IRC channel logs

2024-09-29.log