<OriansJ>rain1: well most distros point /bin/sh to dash, so why bash is an interesting question
<lsl88>civodul: for trying out the tools. At first I recall mentioning that I used some that did not come from inkscape, so I fetched some from previous talks, changed the text, with jokes about my cat, and blaming bjorn about it, and then translated them - I did it manually- . But I did not know that anybody was going to be able to see that.
<OriansJ>also /usr/bin/env bash is the standard for spawning bash anyways
<rekado>janneke: the build just failed with ENOSPC on one of the build nodes
<g_bor>We checked the target options with rekado, and decided to stick with current practice as far as we can by providing a jre image as the output. The jre was removed from the all target of the makefile as of openjdk11 but still can be built using target legacy-jre-image, upstream announced the intention to remove that sooner or later.
<thomassgn>I'm trying to understand and apply trivial-build-system but struggle with just extracting from the tar.xz. I now get no errors from the (invoke tar "xvf") but the build directory (from guix build -K) has no files... Where did they go?
<thomassgn>I realize it's not a "good(tm)" question. I'm also a bit hesitant to ask seeing as the software I'm playing with is nonfree (I have a little list of mostly free and some nonfree packages I'd like to package, this was the first - because I "need" it).
<rekado>thomassgn: they were likely unpacked in the current working directory.
<rekado>thomassgn: have you looked at other packages using the trivial-build-system?
<thomassgn>mm, I looked mostly at markdown in markup.scm and font-adobe-source-han-sans in font.scm as they both use trivial and invoke for extractraction
<thomassgn>I have the (invoke tar...) inside a (with-directory-excursion out ...) I thought that would make CWD be out? Maybe that is not what I want/need afterall.
<rekado>with-directory-excursion temporarily changes the CWD for its body.
<civodul>rekado: ahem, i tried the gdb trick but that didn't quite work
<efraim>thomassgn: if you're 'plopping' it into place then you can look at the 'tar' options to choose destination, otherwise you'll have to refer to 'source' to unpack it while 'in %output'
<thomassgn>mm. should've checked with-directory-excursion, for once my assumption was correct. I'll go ahead and look at some of the free packages like a webapp next time I try trivial-build; so much easier to ask for help and to help out with :)
<thomassgn>efraim: thanks, I'll have a look at that - maybe :)
<thomassgn>as in - maybe that will do the trick (after sending that looked like I meant something entirely different)
<thomassgn>related, is out (usually from '(out (assoc-ref %outputs "out"))') and the temporary build directory in /tmp/ the same thing - as in it is the /tmp/guix-build-... until it completes building and then copied to the store? or is there some other variable I should use for the /tmp/ directory, if so, is the entire build directory in /tmp/ moved to the store after?
<allana>Are there any Python developers in the room? I'm curious about the state of the art of Python development using guix. Recently I have been using nix along with a shell.nix for each project that will create a pure shell environment for that project and call "setup.py develop" for hacking on my project. I'm aware of this blog post: https://trivialfis.github.io/linux/2018/06/10/Using-guix-for-development.html -- and I am curious to know if
<allana>anyone is aware of additional resources or have any tips to share.
<thomassgn>allana: Hey! I'm slightly familiar (and rusty :)) with python. That blog post seems to list wht you'd need. But I'd add direnv - it's pure magic and so simple. :)
<thomassgn>one other neat thing (might be mentioned in the blog - I only skimmed it) is if you create a package definition for your project you can use that as the argument to guix environment. It would also enable you to install the project, share it easily with others using either guix or guix pack. guile-semver was posted recently as a good example for this kind of usage:
<allana>thomassgn: There is a good chance that my Python package(s) wont be packaged for guix for a few reasons, but the biggest is that I am the only guix user in my organization. I seek to use it mostly my own personal development environment. I will likely use guix environment --manifest my-dev-dependencies.scm --container and then develop in python as though I was in any other environment
<allana>baconicsynergy: I got one of those atheros usb long range wifi adapters. It is actually quite nice, I get more wifi access points and better signals
<allana>baconicsynergy: if it is an option for you, you may like it as well. I'm only mentioning it because I was skeptical of using one myself. Now I also use it with other laptops with working nonfree wifi hardware
<g_bor>I was not here from the beginning, what were you trying to do, and what error happened?
<janneke>samplet: i think so...i'll rewrite my commit if that's OK, i just found -e and -x are setting gash style options, reading about setopt!
<necrophcodr>i'm trying to install guixsd on a vps on vultr, so i've booted the iso and installed per the official documentation (with only one btrfs partition and nothing else), and tried running the `guix system init /mnt/etc/config.scm /mnt` command