<ng0>In my VM it seems like it differs. A second opinion would be good, then double checking if some of the other switches are affected by that and will no longer be needed. Then the creation of a patch to drop them. I consider customized variants easy to be produced, but maybe we should have an "tor/hardened"? But if we just drop -expensive-hardening there is still some hardening.
<nckx>civodul: Sorry it took me a while to catch on to what's computed when. I've only started to peek into the world on the other side of gexps last week. Should have started sooner — it's not *that* scary.
<oriansj>wigust: if I remember correctly the majority of guix users don't use guixsd simply because the software they consider essential hasn't been packaged yet or because guixsd is still considered beta software at this point
<dTal>I don't use it ever since I tried to change my hostname and ended up recompiling Samba
<jonsger>oriansj: and they have "problems" with linux-libre
<buenouanq>everything else seems crippled and unusably inadequate to me now
<oriansj>jonsger: that usually simply means hardware without good drivers
<jonsger>I didn't get guixsd run inside qemu so I decided to use just guix
<oriansj>buenouanq: some come for the ease of development, some for the reproducibility and some for the enpowerment of users
<buenouanq>Freedom is more important than capability, comfort, and convenience.
<buenouanq>Luckily, with GuixSD, I can finally have it all.
<oriansj>buenouanq: freedom without community isn't freedom for long
<oriansj>personally I use guix because it gives me a far easier target for my bootstrap project
<oriansj>basically reducing the guix bootstrap binaries down to a hex assembler and an exec_enable both less than 500 bytes
<oriansj>which then are used to make a macro assembler, then a lisp and forth and finally a C compiler which can bootstrap guile
<oriansj>also I am making sure the bootstrap pieces are universally reproducible (aka one could use a c64 to verify everything)
<wigust>jonsger: on guixsd we have a symlink ~/.config/guix/latest to /gnu/store/...-guix-latest which you can point to git checkout if you want to. May be something similiar on guix for other distroes.
<rekado_>I’m not using lsh often enough to remember what key I provided for the build farm.
<rekado_>I remember that I converted an OpenSSH key…
<rekado_>Is anyone else using multiple SSH keys? Is this a good idea or should I just give up and use the same key everywhere?
<rekado_>ACTION configures the bayfront clone to be like bayfront
<lfam>rekado_: I use per-host SSH keys, give them descriptive names, and use ~/.ssh/config to make them easy to use