<ecbrown>i have a package that would normally be installed in /opt/mypackage/, and in that dir is the usual bin lib, plus two necessary static data directories, plus a bit of documentation. is there a guix convention for handling this? i would not want to crap up the ~/.config/guix/current directory
<ecbrown>(though if you are installing this package, you really really wouldn't mind :-)
<efraim>You could swap out '/opt/mypackage' for $PREFIX
<ecbrown>efraim: i guess i meant that it seems that there are programs that fit nicely into /usr/bin, /usr/lib, and /usr/share/myprogram/data-and-whatnot and those that go into an "opt" directory because they are not respectful
<ecbrown>i will work on it some more... maybe that stuff is relocatable
<ngz>Hello. I have an error when trying "git pull" from root: "error: Git error: the SSL certificate is invalid". Do you know what is that?
<civodul>ngz: does /etc/ssl/certs exist, and/or did you set SSL_CERT_DIR?
<ecbrown>ngz: i think you need to make sure nss-certs is installed, and also SSL_CERT_DIR, SSL_CERT_FILE, GIT_SSL_CAINFO
<rekado>I’m having really weird problems, like the derivation that should download the static Guile seems to succeed, but later the derivation that should unpack it fails — and sure enough: the tarball doesn’t exist, only a lock file.
<nlyy>In the context of "To ensure that libraries written in those languages can find library code they depend on at run time, run-time dependencies must be listed in ‘propagated-inputs’ rather than ‘inputs’."
<janneke>the path that such a program uses at run time to look for its dependencies?
<ecbrown>having done this, i have a number of questions, i hope #guix would indulge me
<ecbrown>i had to make a change to openblas. i would like to rebuild all packages that depend on it, and i can get this with guix graph. is there an easy way to just dump a list of dependents of the first level, in textual form?
<ecbrown>i'd even settle for (what seems to be) a better approach and rebuild each dependent, at infinite level
<ecbrown>(basically the change is to insist that the Fortran interfaces are 64-bit on 64-bit machines)
<rekado>but they’d need to be “processed” enough to make for a reasonably challenging and engaging internship project.
<rekado>there should be reasonable milestones and less … “we’ll see what happens, let’s explore this together”
<lfam>I was thinking that the Cuirass web UI would be a really valuable contribution, with specific goals, and that I would be willing to mentor it. But I understand if we'd rather try to make it happen sooner.
<rekado>yes, it would be quite some time before we could reap some usable results.
<rekado>The internship would begin in December and end in March.