<davexunit>by default, it spawns a new $SHELL, but you can instead use the --command flag to run a different program in the environment. so, guix environment doesn't seem to one-up nix shell after all.
<Tsyesika>hopefully by tonight i'll have something packaged X
<davexunit>has a mostly working 'guix environment' script
<davexunit>hmmm how to get the native search paths from a derivation...
<davexunit>from what I can tell, there's no reliable way to pull the necessary search paths out of a derivation
<davexunit>they are part of the builder script, which could be any scheme code.
<davexunit>and I'm unable to obtain all of the packages necessary for a build because of implicit inputs.
<davexunit>if I could only get complete set of inputs for any package, I could simply iterate over their native search paths.
<davexunit>or get a full set of search paths from a derivation...
<davexunit>from what I've read of the nix-shell source, they assume that a phase called 'setup' exists and run it in the new shell.
<davexunit>I think they can just do that because the phases are bash functions.
<davexunit>in guix, there need not even be phases, the trivial build system doesn't have any. there's just a builder script.
<davexunit>I guess I could avoid all of this pain if implicit inputs could be queried somehow. Although, implict inputs aren't constant for a build system. the python build system could use any version of python. This is a tough problem...
<usrnix>Is there a typical package template file for making packages with guix?
<zacts>I think it would be nice to allow for guix to build with the musl-clib as a user option
<mattl>does anyone have a Guix build I could easily run a VM, that's essentially ready to go? I think that might be an interesting next step, to allow the world to see a LiveCD or similar that boots up and lets you start installing things.