<sir123>Hey guys, does anyone know how you could run the guix package through tor? Is there a way to get it to use SOCKS5?
<sir123>Guix doesn't have a way around proxies, I think, unless you could hack a way in? Any ideas?
<zacts>sir123: hum.. I wonder if you could port forward with nftables / iptables or openssh somehow, as a temporary solution
<sir123>I'm thinking it should be a feature request. Not anything urgent. I used to have success with a program called proxychains that would forward all TCP/IP data through HTTP, SOCKS4 or SOCKS5 proxies, therefore would work with tor. I'm wondering if it would be worth asking for commit?
<sir123>I've got the program here, just looking at the code. GPLv2.
<mark_weaver>so, you could add a package or service by editing the files in that git checkout, then running "make" to rebuild, and then using that guix to either build your new package or to run "./pre-inst-env guix system build <OS-CONFIG>" to build a new system with your new service included.
<mark_weaver>and when building emacs, you'll need to set PKG_CONFIG_PATH to include <prefix>/lib/pkg-config
<mark_weaver>so that it finds the right guile. and probably PATH set as well.
<paroneayea>mark_weaver: yeah I tried doing those things but I think I did them wrong :)
<mark_weaver>well, I dunno, I suppose guix would take care of some of those complications for you, but on the other hand, every iteration of trying would involve a rebuild from scratch, so it's a tradeoff.
<davexunit>and if you write a package for that tweaked guile, it will of course be isolated in /gnu/store.
<davexunit>'guix environment --pure' would be ideal for the most isolated environment, but you have to be careful of .bashrc type files overriding env vars
<rekado_>I use "guix environment --pure r" to investigate a test failure; apparantly there's an older version of icedtea6 and guix environment starts grafting icedtea6, which takes much longer than I thought it would.
<mark_weaver>the usual anticipated case for grafting is when patching a core library. in such cases, we don't rebuild everything against that new library, but rather rewrite the rpaths in everything to refer to the patched library, which accomplishes something similar to what happens when you simply upgrade a shared library on a traditional distro.
<mark_weaver>btw, I have found that on my machine (with a spinning disk), texlive takes longer than an hour to graft, which causes guix-daemon to time out after 1 hour of silence. the workaround for now is to pass --max-silent-time=10000 to any guix command that builds stuff.
<mark_weaver>the better solution will be to (1) optimize grafting to be faster, and maybe (2) show time kind of progress indicator while grafting, so that the 1-hour-of-silence timeout doesn't apply.
<mark_weaver>jgay: in brief, we use fontconfig, and we configure it to look for fonts in ~/.guix-profile/share/fonts instead of the default /usr/share/fonts
<mark_weaver>~/.guix-profile points to a user profile, which is itself an immutable tree of symlinks, a merging of all the packages the user has installed.
<mark_weaver>the end result is that the fonts from all the font packages that the user has installed in their personal profile end up into ~/.guix-profile/share/fonts, and fontconfig handles finding them.
<rekado>civodul: I resent it twice or so, but only because msmtp indicated a TLS timeout. I had no idea it actually went out. That it got stuck for being too big made it worse because I was convinced it actually wasn't sent.
<rekado>had this problem only on my workstation in the office, not when going through my personal mail server.