<yewscion>`wrap-program`, but it doesn't say anything about setting environment variables, only that the script should live in the `textmf` tree and a different script needs to call it. Should I just make a `plain-file`, or is there another mechanism for this case?
<bjc>i'm still not sure how i feel about this, but i confess it may not matter as much as i think it does
<vagrantc>bjc: and it is, of course, a bug for something not to build, but it takes someone to fix the build failures
<vagrantc>guix will rebuild a package whenever it's dependencies change
<bjc>on more mundane matters: is there a function somewhere that'll create a file-like-object from a git checkout+path?
<bjc>it'd be nice to pull dotfiles or whatever from git for home usage
<vagrantc>there is guix home for that sort of thing, haven't used it much myself
<awb99_>Is it a good idea to move all the package definitions of my user profile inside guix home definition? It seems guix home does not have options to show installed version numbers or to upgrade packages. Om the other hand this would make it easier as by using guix home for packages I dont have to keep config for system user and home.
<attila_lendvai>i keep seeing "error: failed to compile 'guix/build/clojure-build-system.scm'" and then it goes away after a make clean-go or something along the lines... am i the only one?
<attila_lendvai>the actual error is: guix/build/compile.scm:194:22: In procedure cdr: Wrong type argument in position 1 (expecting pair): #f
<allana>Hi #guix! Is there a way to chain multiple guix commands that follow "guix time-machine"? I have tried "guix time-machine -- build something", and that works, but how does one pass multiple commands to time-machine?
<rekado>allana: there’s no support for that. But “guix time-machine” caches the requested Guix, so subsequent invocations should be faster.
<abrenon>how about shell itself ? Wouldn't it open a prompt at the right version of guix, where the build and other commands could be issued and would see only that particular version of guix ?
<tschilptschilp23>AIM: I've only tried for GNOME -- here I can basically go graphically via Network-Settings -> Wifi -> three dots in window top right -> enable Accesspoint. There one has to set the pw and then even an QR-Code for mobile devices gets displayed!!!
<attila_lendvai>if you were to add a with-syntax* to guix, where would you put it?
<allana>Hey #guix, anyone know of a way to provide a name for a bundle packaged by "guix pack"? For example, when I create a guix pack -f docker and the resulting image has a name like python-python-something-python-something-python-something
<civodul>allana: hi! currently you can't choose the name for Docker images
<jackhill>xelxebar: `guix refresh -l patchelf` says that changing patchelf would cuase 1799 rebuilds, so it should probably be done in the separate 'core-updates' branch. I haven't checked to see if it's already being worked on there.
<jackhill>xelxebar: on darn :(. Anyway, if you're up to it, I encourage youto submit an update (and feel free to ask here if you have questions)
<jackhill>the usual answer to why things haven't been updated is just no one's gotten around to doing it yet. Fetching from git should be fine.
<xelxebar>jackhill: Ah. That's a good sanity check. Thanks. It's mildly curious that the package explicitly sets release-monitoring-url to the github repo but fetches sources from nixos.org.
<jackhill>yeah, I wouldn't have thought there were so many dependents until I checked :)
<xelxebar>Anyway, I have half a mind to try tackling the patchelf bug first.
<awb99>I bought a new usb based wifi card, which I suppose will work with guix. Now I have to add the driver. Can anyone tell me how I can detect the chipset of the card, and where to find information how to add the wifi dirver to it.
<tschilptschilp23>I just found something strange when running ~guix system list-generations~. Some of the listed generations don't list channel and commit information. Even more confusing is, that guix system describe tells me I'm on Generation 45 (with no commit listed), which should feature Kernel 5.16.15, while uname -a tells me it's 5.16.18. And the last Generation 44 matches what I see, and also matches the commit 9bd4ed which is shown by guix
<tschilptschilp23>describe. I guess I messed something up, and am quite lucky to be on a functional system. Any ideas on that?
<yewscion>Hey all, I have a question about convention. The software I am trying to package needs a script that calls the binary package (sort of like a wrapper, but without setting any variables) to be installed in a bin directory, but doesn't package such a script with their source. What is the canonical way to do something like that in Guix?
<tschilptschilp23>mhm. I now switched back to system generation 44, deleted the other generations and reconfigured and am on a proper 45 where commit is shown and aligned with what I expected. And my system still boots. Along this journey I (re-)learned that there's ~guix describe~, ~guix home describe~, ~guix system describe~, all with their own versioning. But no ~guix package describe~ ;)
<vldn>.guix-profile symlink links to the right position?
<tschilptschilp23>I'm not really sure what the right position would be, I pretty much rely on home for that. But as there's now no other generations of anything left after this massacre, I guess so...
<vldn>symlinks from $HOME/.guix-profile to /var/guix/profiles/per-user/USERNAME/guix-profile
<tschilptschilp23>I think it's fine now, it symlinks to the newest thing in ~/var/guix/[...]~ now, and all the mentioned describe commands point to the same commit. Thanks for pointing at that place!
<tschilptschilp23>yes, I think I found the culprit. As I just learned, there's ~guix pull --list-generations~ as well. There where still a few confusing files left in ~/var/guix/profiles/[...], now things look consistant.
<atka>tschilptschilp23: I had an interesting guix update the other day that left me unable to list system generations or roll-back/switch-generations, I have no idea what I did to get to that state. I had to garbage collect everything but the current generation before everything got back to "normal"
<tschilptschilp23>Mainly confusing, because I hardly ever had a look at the place vldn mentioned before. As I understand it now Generation N as returned by ~guix home describe~ should reflect N in the guix-home-N-link file which the guix-home file links to. Generation N as marked active returned by ~guix pull --list-generations~ should map to the current-guix-N-link file which the current-guix file links to. Generation N as marked active by ~guix package
<tschilptschilp23>--list-generations~ should reflect N in the guix-profile-N-link file which the guix-profile file links to. This is all in ~/var/guix/profiles/per-user/$USER/~. And the Generation K, which is marked active as anwer to ~guix system describe~ should be the K in the system-K-link file, which the system file is linked to in ~/var/guix/profiles~. And all these files containing N or K link to corresponding files in ~/gnu/store~. Puh, I hope