<ng0>https://ptpb.pw/G4EV this is inside the /gnu/store/ of what I just installed, so at least on this dir level it looks alright to me
<bernalex>hi. quick question regarding the distro: do you do OpenPGP-signing of snapshots, or something else so that end-users can verify the integrity and be protected from MitM?
<davexunit>bernalex: our releases and disk images are signed
<davexunit>we are working on securing non-release updates via 'guix pull' currently
<bernalex>davexunit: OK, great. I'm looking at differences between guix & nixos. this is an incredibly strong point in favour of guix imo.
<bernalex>OK, so two more questions. with guix -- 1. is it trivial for me to compile things on my own computer, rather than going through a build farm? and 2. is there a large degree of supported customisation of compile flags, à la what Gentoo offers with USE flags?
<davexunit>that would result in lots of nondeterminism.
<bernalex>davexunit: I don't want to have to deal with a billion individual packages to be able to say "I never want you to compile gtk support, and I want you to always compile qt support", as an example.
<ng0>you have to rethink when you come from gentoo, and also consider that GuixSD is 3 or 4 years old and Gentoo is very mature.
<davexunit>bernalex: you can customize packages that aren't to your liking quite easily because they are represented as first-class objects in our Scheme code.
<bernalex>davexunit: yes, but if you can't say '-gtk' or similar somewhere, that sounds to me like customisation is way too much work.
<davexunit>but if you want Gentoo, then I recommend using Gentoo.
<ecraven>php uses the ldap library, lots of other things do too
<ecraven>yes, lots of things are broken, that's not the point :)
<davexunit>I imagine there's a misunderstanding somewhere in here.
<davexunit>I find it hard to believe that a client library reads a file on disk, and only a single hardcoded file that is specified at compile time
<ecraven>I have tried many things, but there's really no good way to change settings except for changing ldap.conf.. it needn't be in /etc/openldap/ldap.conf, it can be in the store, but it *needs* to be modified on installation
<ecraven>I've found an environment variable (LDAPCONF), but that doesn't work (at least not on nixos)
<davexunit>there must be a way to say which file to use
<davexunit>it doesn't make any sense that there wouldn't be
<davexunit>basic argument: "the hello package in guix is 20 lines so it sucks"
<davexunit>it's such a trivial package that it should be no more than 8 lines or something
<ecraven>well, I've learned some APL over the last few weeks, at the start I thought "holy moly, how can you ever program like that", but after some time, and getting to know it closer, things seem better now
<ecraven>great, I'll read that on the ereader while commuting :)
<ecraven>davexunit: you mentioned that guix was built in a better language (I definitely agree) and on a better foundation / api than nixos.. can you elaborate on the "better foundation / api" a bit? that sounds interesting
<ecraven>have to leave, but I'll read the backlog, if you write anything
<suppi>ecraven, I'm currently reading the paper about guix. i think it talks a bit about that so you might want to read it if you are interested
<rekado_>janneke: might be that our lilypond package does not retain a reference to fontconfig. When I run "guix build lilypond" it is downloaded again, but when I ran "guix gc" yesterday it must have been deleted.