<dattashantih3>Is the compiler a library was built with encoded in the guix hash?
<dattashantih3>I was wondering if there was a way to have the same libraries built with different compilers in separate profiles
<dattashantih3>Anyone know how to build libraries with a variety of compilers?
<jackhill>dattashantih3: I think you may have to create a different package that using a different compiler. The different common lisp packages and python2/python3 packages might be good places to look
<jackhill>maybe if we ever get "parametric" packages (like gentoo use flags) it will be easier
<dattashantih3>jackhill: that is unfortunate. I was looking for something similar to spack where I could easily create profiles containing libraries compiled with different compilers.
<jackhill>dattashantih3: indeed that would be neat, but as far as I know that would need code that is not-yet written. I can imagine something that would programaticaly re-write packages to use a different compiler.
<jackhill>Thanks for sharing spack, I wasn't familiar with it. :) Maybe their technique could be implemented with Guix
<jackhill>I see that one of their use cases is HPC. There are Guix HPC people, but I'm not one of them. You may want to ask again when rekado is around or ask on email@example.com
<dattashantih3>jackhill: thanks for the info, I was hoping to use guix specifically for HPC where this is a common use case.
<pkill9>bdju: i want to make a 'url-fetch' that gets the latest git master, so it wouldn't take a hash but just get the latest one, but I don't understand how the downloaders work from looking at the code
<mitescugd>question from someone who is not experienced with either scheme nor containers: isn't it better for guix environment -C to not assert container features? I could then either run with sudo (which already should have cap_sys_admin) or tweak my capabilities
<mitescugd>Or better said, to not assert "unprivileged user namespaces"
<mbakke>mitescugd: guix environment --container only supports unprivileged containers
<mitescugd>thank you mbakke, I looked over the differences in the code to understand more what differences are there
***kdtsh[m] is now known as kdtsh
<mitescugd>privileged containers are just containers run with super-user privileges (i.e: root). afaik unprivileged containers are a source of security vulnerabilities and have them disabled by default. `guix system container` would create privileged containers, as you are only able to run them as root. docker, if the daemon is ran as non-root would basically be unprivileged containers.
<Aurora_iz_kosmos>OriansJ: Alright, I was mostly asking in case I'd missed some relevant section about it in the manual.
<Aurora_iz_kosmos>OriansJ: Do you think there's anything that would prevent firewalld from working on Guix?
<efraim>I think I found a bug in the enlightenment codebase, it only installs the enlightenment-wayland.desktop file if it's built WITHOUT wayland support. I'll have to test if that makes a difference
<OriansJ>Aurora_iz_kosmos: well if firewalld has a systemd dependency in behavior; there might be an issue but honestly I don't know since I don't use firewalld as secure rules can be rather simple: https://paste.debian.net/1108391/
<Aurora_iz_kosmos>OriansJ: The thing is the complexity of rules starts growing wildly the second you try to make something.
<Aurora_iz_kosmos>Even something as simple as "firewall-cmd --zone=public --add-port=8080/tcp"
<Aurora_iz_kosmos>On a somewhat different topic, what's the recommended way of locally caching Guix substitutes to save upstream bandwidth?
<efraim>I run a guix publish server on each of my machines and put them higher than the official substitute servers
<wdkrnls>could the OS installation use these publish servers if available?
<wdkrnls>I'm having trouble completing substitute downloads from the official servers at times.
<wdkrnls>This has so far resulted in 5 failed attempts to install guix on my desktop computer.
<OriansJ>Aurora_iz_kosmos: I've been a big believer of simplicity and isolation; makes it harder to shoot myself in the face.
<wdkrnls>if it was otherwise possible to build a disk image with everything I needed for a minimalist system, that might work even better.
<Aurora_iz_kosmos>wdkrnls: I think that may be possible using the manual installation process, much like one can do with Arch Linux.
<Aurora_iz_kosmos>wdkrnls: It would however be nice to have such an option in the friendlier GUI method