<ryanprior>Okay got it. I've seen some pretty sad slow builds sometimes that only use 1 of my 8 logical cores so I wondered if that was because of a Guix default or what.
<ryanprior>Specifically I remember I built alacritty earlier today and it was using 1 core. That's a Rust app and I don't know anything about the Rust toolchain and don't want to spend the energy to learn right now X.X
<apteryx>some packages have broken parallel builds and are built using a single process
<Gooberpatrol66>so if i make mcron call "list.sh", and list.sh just has a single "ls" command in it, "list.sh" will know where "ls" is located in /gnu/store, just as though i had logged into my user account, opened a shell, and executed list.sh myself
<guix-vits>Gooberpatrol66: Guix Manual, 9.8.2: an example of '#:user "charlie"'.
<ryanprior>Manually specifying 8 cores and 1 job does indeed peg my CPU at 800% str1ngs :)
<ryanprior>Another question that came up the other day: I found a circular dependency in a golang package I'm working on (gohugoio/hugo) It depends on gohugoio/testmodBuilder, which in turn depends on gohugoio/hugo.
<ryanprior>Do we have any way of dealing with circular deps? Or do I need to do something clever like create a source-only package for Hugo that the testmodBuilder relies on, which then in turn the main Hugo package can rely on?
***drakonis is now known as drakonis-
<str1ngs>ryanprior: I hope 800% is good thing :thumbsup:
<efraim>ryanprior: in that case I'd mark testmodBuilder as source-only with a note it only being used to test hugo, which it does when building hugo
<civodul>in Guix you would use 'find-files', which supports regexps (not glob patterns)
<peanutbutterandc>civodul, Hello there! Yes, I think that is what I'll use. I was just wondering if there was something easier (as it's just one binary. Guess I'll just (car) from that list). Thank you
<efraim>where is the 3.3 from? could you use (package-version other-package) to get it?
<Brendan[m]2>perhaps one could implement tinyscheme as a language in guile
<peanutbutterandc>Brendan[m]2, lol. I still need to go through SICP. But I'll put this on my list of things to do someday when I get competent enough and nobody else has gotten around to doing it. :D
<peanutbutterandc>Now, regarding that https://termbin.com/ely1 thing: It seems that that is the way to add further arguments to an inhertied package (guix edit goffice)... so there must be something else going on here. *looking*
<nckx>jlicht: 755 sounds pretty sane to me. Or rather: anything else does not.
<jlicht>hello nckx! it's good 'ol lucky 777 right now for some reason
<OriansJ`>nckx: 750 with the group being users is a good way to prevent system services from accessing certain programs they shouldn't need to access (assuming one doesn't have something like selinux or apparmor running)
<jlicht>honestly, I'm happy with anything that makes sshd happy ;-)
<OriansJ`>jlicht: most programs complain because their programmers were too lazy to think through what the implications would be if say nginx or apache spawned them because of a carefully crafted POST or GET request.
<nckx>OriansJ`: Honestly that sounds like a risky choice that will work until it doesn't, but more due to sloppy programming than a hard need, indeed. I have encountered daemons that barfed when they couldn't open / after I'd restored a back-up badly.
<nckx>Is FILE_OFFSET_BITS a temporary thing until (say) a core-updates merge? Or more boilerplate to remember?
***trava9626 is now known as travankor
<jlicht>unrelated, but is there anyone using Emacs 28-to-be native compilation on their guix system?
<PurpleSym>Is `guix archive --export` broken? It says “guix archive: error: corrupt input while restoring archive from #<closed: file 7f27c396e150>” on two of my machines.
<PurpleSym>Hm, +++ killed by SIGABRT (core dumped) +++ looks suspicious.
<divoplade>Hello guix! I have watched the recent FOSDEM "Universal package & service discovery with Guix A universal functional package manager and operatin..." (I guess it was truncated from operating system), by Pierre Neidhardt and I am glad to see someone talking about data as linked data! I am myself trying to implement the Solid authentication protocol (https://github.com/solid/authentication-panel) in guile with Nettle, and it's not that
<roptat>some translators have, and may be also contributors to Guix, so I don't know
<roptat>also I found where the wrong license comes from, the package name for the manual is "guix", instead of "guix manual", but changing that I get this line: This file is distributed under the same license as the guix manual package.
<civodul>roptat: yeah it's easy, we just need to add a Bazel frontend to Guix and we're done
<str1ngs>janneke: hello, emacsy should support multiple minibuffer. but minibuffer is a global binding and hard coded in (emacsy minibuffer). I'm debating making it a fluid or a parameter. let me know what you think would work best. this would be something I change later down the road. First I need to redo all the tests because there are many cases tests pass but they should'nt due to check.scm.
<janneke>str1ngs: that sounds like a good idea either way; i'm a bigger fan of parameters, although i feel civodul is becoming less and less enthousiastic about dynamic binding in general (the same holds for fluids i guess)
<jlicht>once we have esbuild, we might even be able to properly build node versions > 10.
<janneke>str1ngs: i'd just take the easiest step for you, first -- and like you say, changing it is probably trivial once you gained some experience with that first choice
<ryanprior>jlicht: yes, once I finish my current epic (packaging Hugo, which also depends on esbuild) my next goal is node 13.
<ryanprior>err node 12, I guess that's still the latest stable
<PotentialUser>Hi, im trying to add a printer with lp, i already added and configured cups in my config.scm and installed escpr, but when listing drivers with lpinfo i can only find 2 epson drivers, what should i do?
<nckx>PotentialUser: Just in case: ‘installing’ printer drivers with ‘guix install’ doesn't add them to your system; you need to add them to (service cups-service-type (cups-configuration (extensions (list <here>)) ...)) in your system .scm.
<nckx>Er... well, the CUPS Web UI allows you to manually ‘upload’ a PPD file and it would be copied to /etc/cups, so you could ‘guix build escpr’ to get the store path & do so. That might still break later, dunno.
<nckx>I *think* the actual bug is that our escpr package installs PPDs to /share/ppd/epson-inkjet-printer-escpr/<foo>.ppd instead of /share/cups/model/<vendor>/<model>.ppd.