<phenoble>I have a question: is there a way to get the output of the log, stored in these *.drv.bz2 files deep inside the store, to stdout on a build failure? The manual says that --verbose is supposed to do that, but it doesn't.
<groffer>Hi, I cannot build lyx: CMake Error at CMakeLists.txt:607 (qt5_use_modules): Unknown CMake command "qt5_use_modules".
<groffer>using guix 1a50321752aa92dcb1acdc1d68bddb65dff0a874 on foreign distro; lyx 2.2.3 out gnu/packages/tex.scm:4297:2
***rekado_ is now known as rekado
<rekado>phenoble: on build failure Guix prints the location of these log files so that you can inspect them. Is this not sufficient?
<phenoble>rekado: You have to sudo bunzip2 the archive (or copy it somewhere else first), then open it in a texteditor. While I note the argument that this may be considered "proper" and "sufficient", I am wondering why --verbose could not just dump the log on stdout on failure.
<phenoble>rekado: I guess that depends on what you consider "build output". Me as a user'd expect the information on why the build of a package failed, to be shown on --verbose; if not by default. But that may be just me.
<phenoble>rekado: no, it's probably not always good idea, but still. Let's leave it there. Thanks for the input.
<phenoble>Hm, so I packaged some piece off github. It offers an optional python2 (TWO) interface, for which there's an install rule. The rule determines the site-packages directory from the detected python version.
<phenoble>guix detects python3 (THREE), and hence puts the python2 tool into ~/.guix-profile/lib/python3.7/site-packages
<OriansJ>daviid: I wouldn't recommend it but that is largely because I never personally tried it and tried to remove the bugs
<OriansJ>Also guix tends to like to leverage Linux's containers to isolate it's builds
<OriansJ>Also I don't believe we have a freebsd build server yet; which would mean they would have to build everything from source if it worked
<daviid>OriansJ: thanks, I won't recommend it then, too bad, the person has marjor difficulteis understanding the basic pkg-config ldconfig 'problems' and can't use guile to compile chickadee ...
<OriansJ>daviid: sounds like they need a more hand-holding distro
<daviid>OriansJ: the best is whe we can recommend to install guix on top of their prefered distro
<daviid>it' too bad it's working out of the box on freebsd
<OriansJ>daviid: if I knew someone who used guix on freebsd on their daily driver; it would be a different story but generally it is far better to recommend for platforms after multiple technical people have hammered out their issues on the platform before we let inexperienced users assume it'll work perfectly.