IRC channel logs
2026-05-21.log
back to list of logs
<vagrantc>ieure: the origins are gzip compressed, so i need to decompress them first ... but yeah, that sounds nice. <vagrantc>ieure: currently trying to implement it in a phase ... have some better commits locally, although still struggling at how to apply the compressed patches as inputs from a phase <ieure>vagrantc, Why not download the patch, stick it in gnu/packages/patches, and use search-patches? Is it very large? <stephen0>I need lua 5.1 but if I guix shell lua I get 5.4. I see some lua5.1- prefixed packages, but how do I get lua5.1? <ieure>bjc, Merely a happy accident. I've owned atomized.org since 2004, long before Guix even existed. <ieure>stephen, `guix shell lua@5.1' <vagrantc>ieure: that would be my naive approach, but at least one reviewer did not like that <ieure>vagrantc, Buuuut... that's the normal way <vagrantc>are there any other packages in guix where point releases are patch files on top of a tarball? <ieure>I don't know anything other than linux-the-kernel that releases like that. <ieure>And I guess the Git repo is way too heavy. <stephen0>ahh, so that's how it's done. Thank you, ieure ! <ieure>stephen0, The manual could do a better job of presenting this info, but `(guix)Invoking guix package' defines the package specification syntax. <ieure>vagrantc, You could add a computed-origin which decompresses the patch, and put that into the package's patches field. <stephen0>Still, for the most part, I'm finding the guix documentation and tools to be a little easier to use than the nix ones. <ieure>Never used Nix, took one look at how you define packages and stopped there. <stephen0>I think maybe I like the abuse. I'm in a perpetual state of fumbling with nix, then having eureeka moments where I forget how painful it was to figure out how to do the thing that just clicked. Then I repeat. <stephen0>Despite my lack of familiarity with lisp, guix seems more straightforward. <ieure>I understand Guix and Nix share a good amount, I think the core skills are very transferrable. But even though Scheme is my least favorite Lisp, it's way, way nicer than the Nix stuff. <ieure>90% of the weirdness of Lisp is understandable with two principles: Function calls put the paren on the left side of the function, and don't need commas between arguments; and everything looks like a function call. <stephen0>Yeah, I liked the nix language better than lisp until I started to configure a system for daily use in guix. <vagrantc>i like guile precisely up until i hate it <vagrantc>right now i am on that latter part of the problem <PotentialUser-26>hi! in my config.scm file, i notice ive forgotten to place the field initializer bootloader-file-systems. i dont know where i should put this initializer however, should it be placed under bootloader? <mlxdy>Hello, how about Thinkpad X13 with GNU Guix? <mlxdy>Wifi probably need properiatery firmware, but is it possible to use GPU without binary blobs? <vagrantc>e.g. what module do i need to import to be able to use it? <vagrantc>mwette: odd ... added that but it still was not available <vagrantc>anyways ... found a git repository with all the patches applied ... so rather than distort my take on reality ... seems more reasonable to switch to use git. <mwette>I've been experiencing some weirdness w/ regex routines. <PotentialUser-26>can i share my config.scm here? im having errors where its saying im missing a bootloader-file-system initializer but i dont know where to put it in my file. <ieure>mlxdy, I'm typing this from an X13 Gen 2 AMD, it works fine with Guix, but I use firmware blobs. <ieure>PotentialUser-26, Yes, but put it in a pastebin service, and paste the URL in the channel. Do not paste your configuration directly in the channel. <aloys> /msg *controlpanel set autoclearchanbuffer $me false