<mb[m]1>vagrantc: those suggestions are for variables that have been added to your Guix profile, but are unset in your environment. You probably already source "~/.guix-profile/etc/profile" in your login shell; you can either source it again, log out and in again, or set them manually.
<vagrantc>mb[m]1: thanks for the explanation ... it was not immediately obvious what would happen if i didn't set them
<OriansJ>its odd that guile-wm has only a single public example configuration and that single example can't even rotate between Full screen applications without a menu
<xelxebar>Was just reading through the maling list about LVM support. It seems like one or two people have munged together patches but nothing has been accepted into main.
<brendyn>Is there already a feature to create multiboot systems? I know GuixSD already creates grub entries to old profiles so this could be modified to support creating multiple independant systems with rollback support?
<efraim>looks like I get to build a new guix snapshot after i finish building webkitgtk
<brendyn>But I guess you would still manage it as a single config, perhaps giving each "system" a name or a number, then one can reconfigure them individually, which would update the grub entries for that one system, but not touch the other ones in grub
<ruuda>How can I mark an input as a build-time dependency? I have a package that contains only source code, which is compiled and linked statically in the build process of another package. If I put it in inputs or native-inputs, it is listed by guix size.
<bavier>ruuda: do you list the package itself, or its source in inputs?
<ruuda>The package itself. How can I list its source?
<bavier>ruuda: see e.g. the "stress-make" package in gnu/packages/debug.scm:279
<ruuda>Hmm, after adding package-source it still shows up. But I also copied the source to output as a build step of that package, will try if removing that helps.
<ruuda>No, it still shows up in guix size, but now with "-checkout" suffix
<bavier>ruuda: so there's a reference to the that source in the package's output somewhere
<mb[m]1>ruuda: In some cases we also edit packages to not record build flags for that reason, there is an example in the "php" package.
<mb[m]1>Was someone working on fastboot for Guix? I'm half-way through, but the rabbit hole is pretty deep.
<ngz>I'm trying to track down Scribus' bug (which cannot start properly outside a --pure environment). It tries to use system's Python instead of the one provided as an input. Setting PYTHONPATH does not change anything. Would setting PYTHON_INCLUDE_PATH and PYTHON_LIBRARIES instead help?
<ngz>or does cmake-build-system take care of it, somehow?
<ng0>I'd like to get my 100 rust crates in the branch working (and some more, but 100 are essential), sadly I'm doing many others things already and can't help.. topic for next GsoC maybe? or is this too little for a students assignment for someone?
<ngz>bavier: I already have that output in front of me.
<ngz>I get : open("/gnu/store/snk1lslg3ykmxmf2qjf13x59d6krpkv1-python-2.7.13/lib/libpython2.7.so.1.0", O_RDONLY|O_CLOEXEC) = 4