<rekado>I have a couple of patches (more than what’s on emacs-devel) that are still waiting for copyright assignment (I’ve already sent a signed form), but there’s much more work to be done beyond that before this can be used as an actual browser.
<htgoebel1>civodul: Packages in python.scm are very inconsistent.
<htgoebel1>civodul: While working on the new python-build-system, I stumbled about some issues and I need to know whichway to go.
<htgoebel1>civodul: Who is the one to competently tell who packages should look like in the store (links, copies, .pth-file) and how we want to handle (not not handle) different version of the same package in one environment?
<lfam>BTW, I don't recommend putting it on btrfs, at least with however Debian configures it. If I am building and my automated backups kick in, btrfs may start doing things internally, and then I've seen load go to 40 on a 4-core machine
<ng0>it's comparable to what's inside gnunet now, though the gnunet one includes builds for all databases at the same time :)
<rekado>to build for i686 on x86_64 do “guix build -s i686-linux the-package”
<ng0>hm.. and building an i686 system image would be the same and documented iirc
<ng0>feedback on our mailinglist from someone who's looking to get started: for the casual reader it's impossible to follow the guix-devel list or find info in a reasonable time .. or what it was they said
<ng0>I do some conversation / pr0oblem solving outside of irc and email