<apteryx>could someone look at the docker.scm and tell me if they also think there's an issue with the substitute* directives?
<apteryx>for example, I don't see why we want to return the mangled xxec.Command into exec.Command, nor why we would for LooxPath -> LookPath, as the mangling was done purposefully in other match rules.
<apteryx>seems like some debugging that was left in
<brendyyn>I might not be able to do the best job of explaining iit
<brendyyn>Basically because the project is a whole, not just two separate things, a package manager and packages. It is subject to continuous change and improvement. for example if changes were made to a build system, then all packages of that type may need to be updated
<brendyyn>However, guix has support for channels which allow other package repositories. I hope the guix community will grow as people create their own repositories for things that aren't ideal to have in the main guix distribution
***rekado_ is now known as rekado
<rekado>resttime: package definitions are code, not just data.
<rekado>since they are code we put them where all the other code is that they depend on.
<rekado>this enables us to more quickly change all of the package definitions when underlying components change.
<vixus>so it looks like there's no way to set up the build directory for a package
<vixus>it would be handy to be able to stop at a certain phase
<roptat>you can run guix build -K and interrupt a build
<roptat>then it will keep the buld directory in /tmp/guix-*
<wednesday>nckx: Last night I wrote a program to get all the licenses(unique) from all the pypi projects, you get about 3000 random licenses in before people just copy paste the whole gpl and stuff into the license string ha
<bavier`>are there not logs for failed builds on berlin.guixsd.org?
<joshuaBPMan>Hello, I'm having some issue where my trackpad only moves up and down. Restarting several times does fix the issue. Does anyone have any pointers (that's a good pun), about haw I can start to fix this issue?
<vixus_>What's the correct way to include a patch in a package (that's not in the original source)?
<brendyyn>vixus_: patches can be put into the guix git repo under gnu/packages/patches/
<vixus_>brendyyn: this is for a custom package (in its own channel) though
<ruffni>my machine crashes while trying to install guix sd. after downloading, just after the step `building /gnu/store/BLA-eog-3.26`. any hints how i can resolve the issue and get guix-sd installed on my machine?
<vixus_>civodul: looks like it has to be guix-pkg/vixus/my.patch
<ruffni>vixus_: i don't know. the BLA part before is a long ascii string...
***vixus_ is now known as vixus
<vixus>ruffni: yeah that's the package hash. you might want to have a read through a lot of the manual before installing guixsd (I'm finding it confusing enough after having read a bunch of the manual)
<kmicu>ruffni: what did you change in stock config?
<ruffni>i commented out the mapped-devices part (since i'm not using luks) and changed the bootloader to grub-bootloader
<kmicu>CornBurglar: those packages have not been contributed yet.
<CornBurglar>How does one contribute a package if they write one?
<ruffni>me too! now i installed a desktop (i3-wm) which seemingly succeded (am able to log into graphical desktop). though it raised an exception (maybe due to me running `guix system reconfigure` as root?)....... but no i3-sensible-terminal seems to be installed. any tricks how i can log in directly to console (so i'm able to install some terminal)?