<vagrantc>it might be easier to just use gnu-build-system instead and delete things you don't need...
<stikonas>sorry, another stupid question from me... "guix --version" shows 4c003c5f2d8a2174210f1cb7f0f8b1f5af738952 (so latest master) but "guix search tcc-boot" (tcc-boot can be replaced with gcc-mesboot, same result) finds nothing. Is that expected?
<stikonas>(what confuses me even more that these packages show up in guix graph)
<peanutbutterandc>nckx, So, wrap-program goes inside #:builder itself instead of #:phases? I will try it right now. Thank you
<nckx>peanutbutterandc: net-base in (gnu packages admin) looks like a good example. The trivial build system is good for a single file, or very ideosyncrating builds, but once you have a tarball it can already be easier to just use gnu- and delete or replace 'configure, 'build, and 'install if needed. It will unpack for you, auto-patch shebangs, compress man pages, check the rpath…
<peanutbutterandc>nckx, I see. This is really just a single file - a script to create time-lapses (which is basically a wrapper around ffmpeg). Hence the choice of trivial-build-system, as read on the reference manual; but I suppose I need read more.
<nckx>peanutbutterandc: A single script is certainly trivial material. substitute* and wrap-program will certainly work in a builder.
<peanutbutterandc>Also is there a way for me to be able to see .drv.bz2 logs without `bzip2 -d logfile` (as in something like `zless`?
<peanutbutterandc>leoprikler, Hahaha (emacs-virgin here: tried looking up a tutorial. Got confused. Could exit out of emacs in the terminal: `emacs -nw`, quite ironic. I thought vim users were supposed to joke about others as not being able to exit out of vim)
<nckx>leoprikler, peanutbutterandc: Does vim have no Scheme refactoring helpers whatsoever?
<peanutbutterandc>nckx, I don't really know. I'm only proficient enough in basic vim and don't know anything about the plugins and stuff. Just a n00b really. Not even a real developer. Just a hobbyist. (I'd like to get hired, though. :D)
<nckx>peanutbutterandc: Does the script really call ‘bash’? If not, you don't need to add bash to the wrapper just because it's a bash script.
<peanutbutterandc>nckx, I see. It's just a #!/bin/bash script. Technically that probably means it does call bash (bash-specific parameter expansions are used)...
<peanutbutterandc>But then again, since guix is gnu system, it probably uses bash by default and not sh...
<leoprikler>Actually, instead of adding bash to the wrapper, you want to patch the shebang.
<nckx>peanutbutterandc: That, and shebangs on Guix are always absolute.
<linuxlx>I using the guix on android, I think I should need an option to disable the test of the package.
<linuxlx>guix on android 's chroot is not working, and the /dev/ is not normal.
<peanutbutterandc>leoprikler, Little help again please... the wrapper program still has #!#f as the interpreter and the .real one has #!/bin/bash even after using patch-shebang (once before and once after wrap-program): https://termbin.com/98ct
<alextee[m]>do you have to reboot to make removed stuff go away from ~/.guix-profile?
<peanutbutterandc>alextee[m], removed stuffs, as in packages? They do go away from ~/.guix-profile/bin just so but remain in a generation that one can --roll-back to.
<alextee[m]>peanutbutterandc: yeah like i am experimenting with a font package im making, and i removed it using guix remove. but i can still see its files in ~/.guix-profile/share/fonts/truetype/
<peanutbutterandc>alextee[m], I wouldn't know much about font files but with another package that I just tried removing, after `guix remove package` it is no longer in ~/.guix-profile/bin on my foreign distro
<alextee>peanutbutterandc, nevermind, i forgot i added this package as a dependency on another package!
<peanutbutterandc>alextee, I see. Glad you figured it out. I'm still stuck with my (patch-shebang) issue if you can help. :)
<alextee[m]>ahhh nevermind, it's because i added a dependency on it in another package. forgot about that !
<alextee>^ matrix is acting up again, please ignore
<alextee>peanutbutterandc, doesn't htis work for you? (patch-shebang "<yourfilehere>")
<peanutbutterandc>No, sir. It doesn't. the wrapper program still has #!#f as the interpreter and the .real one has #!/bin/bash even after using patch-shebang (once before and once after wrap-program): https://termbin.com/98ct
<alextee>well, since you have bash you could try this instead: (substitute* out (("/bin/bash") (string-append bash "/bin/bash")))
<alextee>but i would patch the shebang in the "in" file before you install it
<peanutbutterandc>Oh... okay. I'll try that then. It seems (patch-shebang) is more elegant. And the right way to do this.
<alextee>im no expert either, i think the best thing you can do is clone the guix sources and go into gnu/packages and just grep stuff you are looking for
<peanutbutterandc>Nope... still nothing. I will do that again, then (look around in guix sources)
<mjsb>Glad to be in the Creative Space of Guix Adventurers :)
<mjsb>I wanted to ask some curiousities about the Guix System as to be sure to be solving correctly some puzzles
<mjsb>Is it correct to update Root profile by executing the following commands: sudo su - ; guix pull && guix packages -u && guix system reconfigure sys_conf.scm && reboot ? May some additional or alternative commands may be correct ? Thanks
<leoprikler>mjsb: why do you want to update root's packages?
<leoprikler>does "sudo guix system reconfigure sys_conf.scm" not do what you want?
<gnutec>mjsb: To upgrade the packages, use "guix package -u", to upgrade the system, only "guix pull" is necessary.
<mjsb>leoprikler: my initiative came up from an issue i've found with my system clock that you can find on help-guix as "ntpd: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized". The suggestion was eventually trying to get the new NTP service definition commit of September by updating root profile
<amz3>leoprikler: it is in $PATH: $ ls -larh $(which wt)
<mjsb>leoprikler: actually the system reconfigure completed succesfully, but the introduced setting introduced a problem, which "disabled" the launch of any MATE application due to "missing gio-launch-desktop". I've found out that Barbato actually found a workaround, which i'll try :)
<amz3>there is two problems: a) "guix package -s" does not find any package from my channel b) trying to install a package from the channel is failing.
<iyzsong>amz3: did you run 'guix pull'? channels need to built (guix pull), then the 'guix' you run should be ~/.config/guix/current/bin/guix, which have channels in its load-path.
<mjsb>gnutec: thanks for the suggestions. Actually my system uses ext4 :)
<mjsb>since my last generation has the "missing gio-launch-desktop" issue, should i explicitely roll-back to the previous one via guix command, or is enough logging on the previous one and issuing again system reconfigure ?
<leoprikler>you can log in to an older version, but "guix system reconfigure ..." will probably not generate a newer version without the bug unless some fix is applied
<str1ngs>hello, I want to use guix's use-package-modules macro pragmatically. ideally I'd like to pass it a list of symbols. but for now I'm trying to call it in for-each but my for-each lambda argument does not expand. see http://paste.debian.net/1115706
<amz3>Thank you. My shell environment was not relying on the correct instance of guix command. I need to improve on that.
<mjsb>Thanks for the infos, i'll try out the workaround and see" Have a wonderful continuation
<vixus_>Hi all, I hve a somewhat subjective question. For the best maintainability, should packages be installed using `guix install`, `guix package -m` or `guix system reconfigure` (global)?
<peanutbutterandc>Everyone probably knows this already, but today I realized the value of the default behavior of `guix package --search-path`; so once I define and install a package, I can just eval `guix package --search-paths` to figure out which of the inputs are currently being used from outside of /gnu/store.
<sneek>Welcome back peanutbutterandc, you have 1 message.
<sneek>peanutbutterandc, nckx says: Well caught: of course shebangs are always absolute. Shebangs on Guix [should] always point to a specific /gnu/store/… binary, which is what I inaccurately meant by ‘absolute’. This will ensure that your package keeps a reference to (=dependency on) bash. /bin/sh on Guix System isn't guaranteed to exist. If it does, it could point to anything. I hope that makes things clear.
<peanutbutterandc>Turns out I was using sed from my installed packages and had to add it to (wrap-program)s. I hope that'll help someone out. :)
<alextee[m]>nckx: yeah i'll need to write a small program for this. ill ping you when it's ready!
<leoprikler>meh, accidentally wrote three messages instead of one :(
<bluekeys>OK, it's like the manual keeps growing before my eyes, though I'd swear I'd read it three times already. Just noticed the lines about git send-email that may have helped earlier too. I'll get to ameding it ASAP.
<kmicu>Today’s gem: “P.S.: I understand that some of this question may hurt some foss boys and girls. But, games are important for me and I really like guix...”
<leoprikler>Sometimes i read Guix ML as "Guix Markup Language" and wonder why that doesn't exist yet.
<leoprikler>Implying FOSS and games are mutually exclusive...
<kmicu>(Where ‘games’ = ‘proprietary games’ cuz we already have libre games in Guix and libre games channel exists on IRC)
<fnstudio>hi, currently trying to compile guix-1.0.1 on a debian unstable but don't seem to be able to find a dependency (guile-git); any idea if i'm missing something or should i also compile that from source?