I wonder if there are any #guix maintainers willing to take a look at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=70112 . I tried asking in #guix room few times, not much luck. There are already new versions available, and I would prefer not to rebase it (again), testing it is quite annoying due to differences between podman 4 and 5...
I ran an experiment yesterday, and found the package with the largest number of dependencies in #guix using this little command: guix package -A | awk '{print $1}' | parallel 'echo -n {}; echo -n " "; guix size {} 2>/dev/null | tail -n +3 | wc -l' | sort -n -k 2 | tee ~/Documents/sorted_packages.txt. The whole thing took 6 hours to run at about 90% CPU utilisation.
Result: pigx has the most dependencies at 968, with most of the runner ups being scientific analysis tools too. Cool!
Consider: #Guix / #Nix shared hosting where the cost of storing a store item is shared between the users that depend on it.
Maybe with the new Shepherd on Goblins integration a shared guix-daemon could work.
@mntmn, @daviwil
Do you guys see a way to have a reform next with #guix as pre-installed system? It would be awesome! But I wonder how is the #guix support on ARM... 🤔
Looking for some Friday #guix reading? How about the next step in the #packaging tutorial? Overview of the build-system concept, and how to provide arguments. We meet the #guile#scheme repl (guix repl) to discuss when to use 'quote' and 'quasiquote' in package definitions.
Oof, guix doesn't seem play nice with foreign distros, even stable ones like Debian. The guix system distro is out of the question because of my WiFi drivers and until nonguix is more mature there really isn't a good alternative for me.
I don't love it but I'll probably have to hop back over to nixos and see how the community changes play out. Good thing it takes like 2 minutes to get my old config back. Still, nix has made it tough to use anything else.
@abmurrow
When you run a bash script, it is not run with same system environment that you have, instead it creates a subshell. For this reason, most probably you didn't have the #guix profile there at all. One way to bypass that is to use source script.sh instead of bash script.sh to run the content of the script in the current bash.
The way I use guix is to have certain tools and containers in guix on a rolling release distro like Arch or Manjaro as the host.
And a 3rd one, Monday 13th of May, at BeCentral this time! There will be again pizzas 🍕 paid by the #NixOS foundation (with Vegan options), and I will bring my X230 (on which I installed #Guix last weekend) for a little demo :D