<rekado_>a presenter there would be among docker enthusiasts; "guix deploy" hasn't yet been tested in production enough to make it easy for a speaker there. By November it'll certainly be good enough, but not in two weeks.
<davexunit>hehe, 'guix deploy' can only deploy local VMs with static IPs right now. definitely not ready for "production".
<davexunit>it could be noted as a WIP that is promising, though.
<davexunit>'guix environment' makes it so damn easy to compile guix and my personal software projects on new machines.
<rekado_>davexunit: a call-for-papers for a conference --> "The event will focus on the lifecycle of software applications with special attention paid to the processes and tools from areas such as Continuous Delivery, DevOps, and Containerization."
<davexunit>I'm afraid we don't yet have much to offer in that area
<davexunit>but... we're working on it, and it would be good to introduce Guix to a wider audience that might want to help us.
<davexunit>if they can get over the fact that we're a GNU project.
<rekado_>well, everything looks like a nail to me now that I have this great hammer.
<mark_weaver>efraim: natively-built tarballs are generally better than cross-built ones, so when I bootstrap a new platform I start by cross-compiling them, and then use those to natively build another set of bootstrap tarballs.
<mark_weaver>efraim: well, you will end up using our pre-built bootstrap tarballs even if you build 'guix' from source code.
<mark_weaver>when you start actually building packages using guix, even if you don't use our binary substitutes, it will start by downloading our pre-compiled bootstrap tarballs for that platform.
<mark_weaver>efraim: what are you trying to do? most users shouldn't need to concern themselves with the bootstrap tarballs manually.
<efraim>I'm trying to put together a guix image for an armhf board I have
<mark_weaver>efraim: but yes, those are the bootstrap tarballs, and there are also a few pre-compiled binaries in the guix "source" tarballs as well, in gnu/packages/bootstrap/
<mark_weaver>efraim: note that we currently lack binary substitutes for armhf-linux, so you'd have to build up the entire system, including compilers, from source code, starting from our bootstrap tarballs. so you'll need a rather powerful armhf board: at least 1 GB of RAM, and a fair amount of reasonably fast disk.
<mark_weaver>we are still awaiting a donation for our build farm to provide binary substitutes for armhf.
<efraim>mark_weaver: I also have a 16gb sd card and 4usb ports. also slow, and could very well kill the sd card, but should be big enough
<efraim>i saw that there are some armhf binary substitutes ready
<mark_weaver>I have a large SATA hard drive in my armhf board (Novena), which was more than enough. I don't know off-hand how much disk space is actually required to build up the system from source code. I suppose it depends on what software you want to build.
<efraim>the kernel failed to build on my laptop when my /tmp was only 1GB
<mark_weaver>efraim: we currently provide only one binary substitute for armhf: guix itself, just enough for you to run 'guix-daemon' and 'guix' itself.
<mark_weaver>efraim: when you ask that 'guix' to build anything, it will start by bootstrapping the system up from the bootstrap tarballs, using a process not wholly unlike "Cross [GNU/]Linux From Scratch".
<efraim>i think i got confused by my bootstrap effort offering to download bash,gcc,etc, but they're also listed as having to be built
<mark_weaver>efraim: there are several phases of bootstrap. the bootstrap binaries are statically-linked, minimal, and somewhat handicapped in various ways.
<mark_weaver>taylanub: do you have any info files in that directory? we added that feature a long time ago.
<taylanub>mark_weaver: yes, they're all there. by the way I noticed guix doesn't build an ...-info-dir (or however it was named) store item anymore when making changes to my profile.
<taylanub>I would always get three things listed under "things that will be built" when making changes to my profile: the profile itself, the info-dir item, and the third I forgot. currently it only lists the profile itself when I make changes to my profile. this is since I updated, recently.
<taylanub>oh wait, it's fixed now. it must either be a bug that has been shortly present in master, or it shows up arbitrarily.
<taylanub>(I just made ~/.config/guix/latest a symlink to ~/src/guix, then installed something to test. hm, let's see if I can find the previous symlink target so I can try to reproduce.)
<taylanub>yes, I can reproduce with 84dv0z07xg8sdglargkdzwf0w2r1gxp0-guix-latest (don't know how to find which git commit that's from). this must mean it's fixed in master.