<Aurora_v_kosmose>Naturally Guix has the same ability as Gentoo on this aspect, though perhaps not the same build flag defaults (as it would hinder reproducibility on machines that lack such instructions).
<Aurora_v_kosmose>If dynamic detection is implemented in GCC, using it by default might be viable and reproduce the same benefits as Gentoo in Guix (minus some disk space).
<xelxebar>AFAIU, gcc doesn't automagically do any runtime instruction detection. That's typically something that the engineers stuff in and build "fat binaries" with microarch-specific execution paths.
<Aurora_v_kosmose>Yeah... I know gcc has explicit multiversion support, but implicit would be significantly more useful on a distribution level.
<Aurora_v_kosmose>As otherwise you effectively have to build all packages for your system locally to have the same benefits.
<Aurora_v_kosmose>Which I suppose might be as simple as modifying the global gcc build-system definition to include those flags
<xelxebar>Yeah, it would be nice, but the tradeoffs are non-trivial, no? Detection itself is a non-zero (albeit small) and somewhat tricky overhead, while carrying around enfattened build products has the obvious size overhead.
<Aurora_v_kosmose>Indeed. How worth it it'd be for a distro depends on how much it minds such bloat. Some programs might see very little bloat, while some might more than double in size.
<kitty1>some non-free protocols can also be bridged with free ones, but generally if possible I think most people (including myself) in this community would just try to convince anyone else to use free software if at all possible lmao
<FlaminWalrus>Anyone have an example of a package definition that uses an origin snippet to remove a file? I'm still trying to wrap my head around gexps...
<littlebobeep>How much RAM is necessary to compile ungoogled-chromium and icecat?
<jpoiret>FlaminWalrus: make-linux-libre-source in gnu/packages/linux.scm does that
<FlaminWalrus>jpoiret: thanks for the tip. Any idea why some places the gexp #~(begin...) is used some places and just the quote '(begin...) in others?
<jpoiret>historically, gexps came pretty late in Guix, and package build phases used simple S-Exps instead (eg '(begin ...))
<jpoiret>all of the packages are being moved to g-exps but it takes a lot of effort
<jpoiret>you should definitely use gexps for new code
<xelxebar>Aurora_v_kosmose: That might be intentional. I don't think properties is intended for generic use, really. If you dig around in the repo, it seems to be mostly a place where internal and "obscure" package info is stored.
<lamdacore>hi, I am attempting to setup a fresh guix in a logical volume (LVM on luks to be precise with a separate boot partition). Could anyone help me /give me hints on how to make dual work work in such a setup? I am using systemd-boot
<bjc>seemed like starting with a vm image that has the disk set up correctly and then running the reconfigure commands inside it would be the most straight-forward way to go
<jpoiret>bjc: rather, you should run the installer iso in a vm and do a manual installation i think
<jpoiret>in any case, you'll have to partition the disk, either through the graphical or manual install, and for lvm you'll need the manual one
<milia[m]>Sorry to ask... What are the most striking differences of guix comparing to NixOS?
<jpoiret>bjc: right, but that requires significant work
<lamdacore>I see. yeah. i saw the linked initrd and images and didnt know how to proceed.
<jpoiret>my (very personal) opinion on the matter is: if you know what LVM is, you most likely can manage a manual installation which will serve you well
<lamdacore>so which bootloader type should I chose here? "grub-efi-bootloader"?
<bjc>jpoiret: i figured it would, which why i'm trying to do as little at a time as possible while still being useful. which i think is getting support in vm image creation, to be able to have a test bed for future work
<apteryx>the Guile default port encoding is ISO-8859-1? Heresy.
<jpoiret>depends on whether the locale is initialized
<apteryx>where is this mentionned in the Guile Reference manual?
<jpoiret>in Encoding, right under %default-port-encoding
<apteryx>"The ‘%default-port-encoding’ itself defaults to the encoding appropriate for the current locale, if ‘setlocale’ has been called.", OK. And how does setting this to #f end up choosing ISO-8859-1 as the encoding?
<apteryx>ah, I need to slow down and actually read :-) "As a special case, the value ‘#f’ is equivalent to ‘"ISO-8859-1""
<bjc>in your system configuration you can manually create the .desktop files and then symlink them to the appropriate place (which is probably somewhere in /run/current-system/profile/share, but i haven't verified that yet)
<bjc>oh.. i don't have a session manager installed. no wonder i can't find it
<bjc>well, on manjaro it's /usr/share/wayland-sessions, so presumably on guix it'd be /run/current-system/profile/share/wayland-sessions
<apteryx>zacchae[m]: can you share a minimal reproducer? I used pip in a venv minutes ago
<EMax`0Mancer[m]><bjc> "well, on manjaro it's /usr/share..." <- ok, not at my guix machine at the moment, but will I be able to symlink into /run/current-system/profile/share/wayland-sessions? I thought this was read-only.
***lh is now known as hupfer
***hupfer is now known as lh
***hpfr is now known as lph
***lph is now known as hpfr
***lh is now known as lhindir
***lhindir is now known as liamiam
***liamiam is now known as lmhpfr
***lmhpfr is now known as lhupfer
***lhupfer is now known as liamhupfer
***liamhupfer is now known as lh
<apteryx>EMax`0Mancer[m]: I believe they meant symlinking the other way around
<EMax`0Mancer[m]>apteryx: what would that look like? I thought gdm is looking in /run/current-system/profile/share/wayland-sessions