<PotentialUser-33>how can i add a channel as i am installing guix? i want to use some packages from a certain channel in my operating system configuration. i am manually editing the /etc/config.scm file during the installation process
<nckx>Sisyphe[m]: Just a guess, but that smells like you have a ‘name’ in your (quoted) build-side code that should be a ‘,name’, since ‘name’ is indeed only defined on the host side. Could that make sense?
<nckx>tune: It will work without the file-system section, you're just responsible for mounting it yourself before running reconfigure. Can be used as a sort of fail-safe, I guess. There are people who don't like to keep their EFI partition mounted all the time because it can corrupt in some corner (crash) cases.
<nckx>So GRUB is complaining about a missing ‘i386-pc’ (non-UEFI) file when invoked as ‘grub-efi’ :-/ Weird.
*nckx just tried Sisyphe[m]'s code in a REPL; of course it works fine. Hm.
<efraim>Isn't name previously defined as the name of the package?
<efraim>I know it isn't unquoted but it's not a variable name I would've chosen
<nckx>Sisyphe[m]: Are you getting any other warnings or errors? That's not the conventional way to import modules into build code, for example (grep for #:modules for examples), but I don't know off the top of my head if it could work.
<nckx>efraim: It is, but it really shouldn't matter.
<Sisyphe[m]>I already have #:use-module (ice-9 match) at the top of my module but removing (use-modules (ice-9 match)) in the lambda causes Unbound variable: match-lambda
<nckx>Is this just for debugging while writing your package? TBH (and sorry for implying you should ignore bugs instead of confronting them head-on), I just always use ‘(invoke "ls -…")’ in such cases. Less typing than doing it properly in Guile.
<Sisyphe[m]>nckx: thanks, I would have liked to improve my guile skills but it's actually a lot simpler
<nckx>Yeah, I feel appropriately dirty for suggesting that…
<Sisyphe[m]>nckx: too late... I'm gonna use that everywhere from now on...
<nckx>I've always found FTW a bit baroque for my few casual use cases.
<nckx>I've heard people say that you don't actually need to learn Scheme when installing Guix System, and fervently disagree. Frustrated users & dreams are thattaway.
<bandali>it’s kinda like “do i need to learn haskell to use xmonad”
<bandali>many would say no, and it’s partly true, but you’d pretty much be trying to copy paste and salvage things from others’ configs
<bandali>whereas knowing haskell (or in this case guile) would actually be helpful in understanding to some degree what is actually going on, and what the expressions you write in your config file(s) actually do
<nckx>bandali: Yeah, I wasn't sure how to word that. If you're willing (and, hopefully, eager) to learn Scheme ‘hand in hand’ with Guix, you'll be fine. But saying that it's optional (as I've seen done) will send the wrong message.
<nckx>yu44: Running such binary blobs isn't really supported on Guix System, although I've heard of an FHS service floating around that can make them work.
<nckx>LD_LIBRARY_PATH won't help binaries find their ELF interpreter (usually hard-coded to /lib/ld-linux…, for example).
<yu44>I am not running firefox-bin, balenaetcher.appimage. Error: File not found
<pinoaffe>I made some changes to guix (my tree is at https://gitlab.com/pinoaffe/guix_fork/tree/fpga ), but when I try to run `guix pull` it throws seemingly unrelated build-time errors for guix-extra, stating that it's unable to find patches for icecat - any idea what the cause might be?
<nckx>yu44: ‘I am not running firefox-bin’ — why mention that explicitly? Are you referring to a previous discussion?
<nckx>Not about that, but I am unsure whether these nublob formats act as a single executable or whether you need to ‘unpack’ them and patch every single embedded binary. I don't expect ‘patchelf foo.appimage’ to Just Work. With some luck, I'm wrong.
<nckx>Oh, wait, I forgot, I'm never wrong. Damn it.
<str1ngs>though if it's an elf then in theory you could use a file server to provide the dynamic linker. and the appimage should work. since it's self hosting
*nckx can't bring themselves to care about these fads. It's design by PR: lobby upstreams to use your ‘universal’ binary blob format, knowing full well that it's the *distributions* that will have to do all of the work. But that's because I'm a cranky zealot who cares about practical software freedom.