<grantixx>Also, I decided to go "all in" and am installing GSD on my other primary box! The only non-Guix centric box I have now is my HTPC and I'm slowly working towards Kodi on that front.
<rekado_>how can I get even closer to the build environment under which guix build operates? I cannot seem to find out why this configure step fails under guix build but not under guix environment --pure.
<rekado_>I would like to "see" and explore the actual environment used by guix build and investigate the error there.
<rekado_>it would be helpful if there was a way to reproduce this environment even more faithfully.
<taylanub>I tried launching an interactive shell from a build phase once via system* but it didn't work, probably due to how stdin is handled. maybe one can open some other communication channel
<ewemoa>rekado_: may be "guix environment ..." is relevant?
<rekado_>ewemoa: I *have* been using "guix environment --pure ...".
<davexunit>I'm currently hunting down something similar
<mark_weaver>rekado_: I gave an okay to push 'ganv', but just realized that "Gtk" should be spelled "GTK+" in both the synopsis and description. if you could fix those before pushing, it would be good.
<rekado_>mark_weaver: will do. I'll only be able to push in a couple of hours anyway.
<rekado_>(still in the office, so I'll only do work-related packages.)
<mark_weaver>I've tried multiple monitors after logging into xfce, and it doesn't seem to work very well. it treats the whole combined screen as a single monitor. but maybe I'm not doing it right.
<grantix>mark_weaver: Yeah, there's a way to turn the whole display off and update it and it works fine iirc -- but I don't know how to set that via Slim.
<grantix>I'm bassically using my Laptop as a desktop, so I'm not using the built-in display.
<grantix>I mean, once you get into the session it's not a big deal because you can have it evaluate a .xsession file.
<mark_weaver>grantix: it may be that you need to modify your xserver.conf somehow. see gnu/services/xorg.scm
<mark_weaver>at least for a way to hack it temporarily for yourself.
<mark_weaver>ultimately, the solution may be to get a better display manager working. I vaguely remember hearing that slim development is not very active, if at all.
<grantix>mark_weaver: Yeah, LightDM is kinda the modernish and activish solution.
*grantix will look into it a bit more, likely. He really isn't even going to touch that box until Wed likely. :^P
<mark_weaver>sure. I've never tried LightDM, but based on what I've heard it would be a welcome addition.
<mark_weaver>and if it's more actively supported and works better, we should just switch to it IMO.
<grantix>mark_weaver: Well, based on release dates -- SLiM last got released at the the end of 2013. LightDM a month ago. Before that, LightDM got released pretty regularly and SLiM had one release in 2013, 3 in 2012, then none between then & 2008.
<grantix>a_e: I typically use Arch's online package interface to list depends (feel free to tell me a better way" and one of the depends are "qt5-base" and I'm not sure if it's just a welrd way they package things or if it's really split like this. That being said, the don't typically move far from upstream.
<a_e>mark_weaver: Then our qt package should work. It should be a superset of qt5-base, logically.
<mark_weaver>buying into the Novena is about supporting the creation of a laptop that was designed with us in mind, as opposed to Intel, where their modern systems simply cannot be used without huge binary blobs and back doors.
<a_e>mark_weaver: Agreed. On the other hand, it is crucial to have a fast development machine also. So currently, it looks more like an additional machine than one that could replace my laptop I use for almost everything now.
<a_e>rekado: It happens in a bash script. Did you have a look at it?
<mark_weaver>intel looks to be a dead end for the free software movement