<a_e>I am updating a few packages, because it is almost a background activity, but requires a bit of waiting for the builds. I suppose that I should not update parted in master, nor help2man (which induces a rebuild of grub)?
<pjotrp>Is it better to build in degraded mode when developing packages?
<bavier>is there any way to get the number of current build threads available?
<mark_weaver>bavier: civodul may have a better answer, but guile has (current-processor-count) and (total-processor-count). the first of those might be appropriate here.
<mark_weaver>civodul: regarding my earlier outline here of how grafts could be done, I should have emphasized that if package A has an input B, and B has an input C which is grafted, then B is also implicitly grafted, so the hash substitutions for A must include not only rewrite rules for C, but also for B.
<bavier>I'm just now reading back on the "graft" discussion. Is the idea that we'd be able to apply security updates to packages without changing their hashes, so that they could be used without needed to rebuild packages that depend on them?
<mark_weaver>bavier: no, the hashes of everything would still change, everything would technically still have to be rebuilt, but the rebuilds would mostly only require making copies of the existing build outputs with hashes rewritten.
<mark_weaver>e.g. if package A depends on core package C, and then C is updated to C2 with a security fix applied, then A2 will be rebuilt from the outputs of A by replacing references to C with equivalent references to C2 (notably in the rpaths used to find shared libraries)
<isd>ui gripe with the usb installer: the boot process doesn't give you a prompt until you hit enter; I was waiting for it to "finish booting" for a minute or two before I poked it and discovered it was done.
<isd>Also, I will glady fix this when/if I find the relevant source.
<davexunit>if you have the prerequisites, you can run: autoreconf -vif, ./configure, make
<davexunit>keptagon: good luck! let us know if you have other problems.
<keptagon>It might be useful to have the #Installation section link to the actual download page rather than the top level gnu.org/software/guix page.
<isd>So I'm doing a usb install, and realized I didn't do the -L when formatting the drive - I'd like to use labels, do I need to do anything to undo the cow filesystem setup or can I safely just umount and try again?
<davexunit>isd: when I screwed up installs, I would just rebuild the filesystem on the partition I was installing to and try again.
<isd>Yeah that was the plan - I just did a deco stop before unmounting, hopefully that is the right thing.
<davexunit>I haven't actually used the OS in awhile. I'm currently running guix atop debian.
<davexunit>I need a spare computer to use for installations.
<isd>Seems to still think it's busy -- I'll just reboot
<isd>I'm trying to set up the package manager on my existing system in parallel, and make is giving me an error about a missing requirement called "dot" which is not mentioned in the readme. I don't know what that is?
<mark_weaver>isd: it's just for rendering a sample dependency graph for the manual. in the past, I've sometimes just used 'touch' to create the file it's trying to build using 'dot', and it only means you have a missing graph in your manual.
<isd>So, another question: feh doesn't have a configure script, but instead you pass options like --prefix= as PREFIX= to make -- I can tell it not to run the configure phase, and I can pass arguments to make via one of the keyword arguments, but what should I specify as the prefix?
<isd>I don't suppose there's documentation somewhere about how to specify the hash? there's the example in the manual, but it doesn't seem to like my idea of base32.
<alezost>isd: Indeed it shouldn't be (sha1 (base16) ...). It should be (sha256 (base 32) ...)
<isd>alezost: yeah, I assumed that wouldn't work but was just getting started -- I changed it to 256/32, and converted the string, but it's giving me errors about invalid characters (things like the letter o)