<g_bor>I've been wondering how can I do this: build all dependencies of a package, but do not build the package itself. I see that I can do this with the sources...
<marusich>g_bor, if by 'dependencies' you mean 'inputs', then something along the lines of what 'guix environment my-package' does is what you're thinking of, right?
<g_bor>Oh yes, you are right, I just had a feeling that sometimes guix environment build more than what is strictly needed.
<marusich>That might be true. Ricardo mentioned in chat and also on the email list (I think) that "guix environment" might be building more than just the direct dependencies (and it might not be intended).
<g_bor>Ok, thanks. I've also seen that mail, and also noticed some extra derivations built... But for my present use case I guess this is acceptable.
<g_bor>I intend to mark #30104 as easy, so that outreachy applicants willing to work on guile tools can have a look at another build system, and fix this trivial bug. Actually all that needs to be done here is already in the mails. I nobody comes up, I will fix this. WDYT?
<sneek>bnw, OriansJ says: that the stage0 vm is going to be gaining support for 256bit address space and registers.
<OriansJ`>bnw: we talked about you writing a lisp operating system If I remember correctly.
<bnw>OriansJ`, no. Sorry but I think you mistaken me for someone else. :-)
<OriansJ`>bnw: Sorry about that. Its just rare to find people who take an interest in bootstrapping work and I certainly enjoy those conversations.
<bnw>ACTION is just a temporal guix user. But still don't have a lot of time hacking it.
<thorwil>hi! how does one handle building in-development stuff on guix sd? where on a common system, say for some unfinished library, one might git pull from time to time and install to /usr/local?
<janneke>thorwil: not entirely sure what you mean (never installed anyting in /usr/local), but i guess the answer is: create/update a package and install it (or enter into an environment where you install it)
<thorwil>janneke: one aspect is that i'm left wondering whether a piece of software that won't run right out of a build tree can be gotten to work without writing a recipe for it
<janneke>thorwil: well, technically nothing forbids you to do ./configure --prefix=/usr/local|$HOME; make; make install -- but creating a package description in trivial (for well-behaved software) and so much nicer in Guix[SD]