<ryanprior>It would be nice if you could omit it in cases where you don't care
<ufjvp>lfam: Okay, thanks anyways. I'll try to build a new installation image tomorrow and see if that helps
<Rovanion>I'm not sure how Scheme works, but I've used Clojure quite a bit. If one were to stick a macro in there you could capture the symbol/name as well as its value. (For a future API)
<ryanprior>The reason you would care is if you need to refer one or more inputs during a build phase. For example, you might want to copy files from inputs into your build tree.
<ryanprior>A macro could definitely clean it up. I am useless at writing Guile macros though, I've read and re-read the docs and looked at lots of examples nothing's clicking.
<leoprikler>I have mixed feelings about using a macro there. On the one hand, yes, it would make typing simpler, on the other it would be a burden to read in many cases and a real hassle when you want to reference the input
***lukedashjr is now known as luke-jr
<rekahsoft>Hi all, I would like to use the latest commit off of master for emacs-treemacs-extra, which implies I need to modify emacs-treemacs as emacs-treemacs-extra inherits from it. The best way I can think of doing this is defining a emacs-treemacs-<commit> package which inherits from emacs-treemacs to use the appropriate version, then also define another package emacs-treemacs-extra-<commit> that inherits from my emacs-
<rekahsoft>eemacs-<commit> package. Is there a better way to do this?
<ryanprior>leoprikler: I picture a macro like ((symbol [optional string for name]) ...) that would get transformed into `((,(or name (package-name symbol)) ,symbol) ...)
<ryanprior>So what you'd specify now as (inputs `(("mypkg-5" ,mypkg) ("libfoo" ,libfoo)) could instead be (mypkg libfoo), and if you want to refer to libfoo by a special name, then (mypkg (libfoo "foo.so"))
<ryanprior>In some other lisps I'd feel confident in putting such a macro together as a proposal, and I may give it yet another shot in guile here some time, but my attempts thus far have ended in defeat.
<ryanprior>rekahsoft: there's CLI flags to do what you want I think! Something like: guix package --with-branch=emacs-treemacs-extra=master --with-commit=emacs-treemacs=<commit> -i emacs-treemacs-extra
<ryanprior>leoprikler: I haven't figured out outputs at all and need to to do, because I'm packaging a number of things in go-land that have a bunch of outputs from one repo
***sneek_ is now known as sneek
<Guest67>Happy Holidays everyone. I need help in "activating' an emacs package; pdf-tools. I installed it using Guix repos and the command will not show up after M-x. I already tried to put either (pdf-tools-install) and (pdf-loader-install) in .emacs but I kept running into errors saying that the command is void.
<Guest67>I've also tried guix-emacs-autoload already
<ryanprior>rekahsoft: cool, if you get it working I'd love to see exactly what you did, I'm still figuring out transformations and gexps myself
<donotshake[m]>Currently using proxmox, ansible, and a few bash scripts to run my environment. I read the Ganeti blog and am interested in switching. Problem is my devops is mostly crude automation using cron and bash. It works great, but isnt declarative. With guix I see a way to define my entire environment in 1 place, maybe using a got service for it all.
<donotshake[m]>I get this is basic devops shit but would extremely appriciate a guix example page with various environments one could deploy in a test lab. The manual is great, im just too lazy to build it myself beyond what I have which seemed easy.
<donotshake[m]>Also making the guix installer / system.scm script generator available online is a great idea. Click all the things, get scm to run.
<ryanprior>donotshake: I'm also an Ansible user who would like to switch some workflows to use Guix, but I haven't worked out how to manage service deployments yet. I could also use that example page with a test lab.
<rekahsoft>ryanprior: Sounds good! Still haven't got it working yet. Have something that I expect to get working, but having odd issues with something simple that I would expect to work: 'guix build --with-branch=emacs-treemacs=master emacs-treemacs'. This ends up with a failed build saying that chmod is missing..
<abcdw>leoprikler, tried to use mixed-text-file, again it was not what I expected) it inserts the path of the file, but I need the content of the file. Is it possible to achieve somehow without using gexp/ungexp?
<leoprikler>abcdw: Inserting the path of the file is all you need – pa script has the ".include" metacommand.
<abcdw>leoprikler, ok, it's reasonable) but in general case, when configuration language doesn't support includes?
<leoprikler>Then you need to some trick to extract the file contents, which probably takes some gexping.
<davidl>dftxbs3e: thx for the Nextcloud links, I tried it out, and managed to compile 2 different versions of it, but they both fail at runtime with [ fatal default ]: Could not find QtWebEngineProcess where I am currently stuck at.
<davidl>I installed a childhurd but I need to increase the disk-space on it bcz installing packages always fails with no disk space left. So I tried to install gptfdisk and thought I could add some disk space and fix stuff, but not enough space to install gptfdisk either - how can I fix this for a childhurd service? or do I need to build a hurd-VM if I want something to fiddle with?
<allan`>Hello, I am trying to write a cron job that starts the program powertop on boot, but I am getting the error "wrong type argument", and I'm not sure what it means. Any thoughts? Here is the code I wrote. https://paste.debian.net/1178315
***spk121_ is now known as spk121
<aecepoglu[m]>I'm going to share a Golang package with the community. It's an executable. Should it still share the `go-github-com-<username>-<repo-name>` naming scheme? I have named my library dependencies that way but I felt like the executables may have an exception?
<ryanprior>aecepoglu: you can name it according to its common name, the go-* naming scheme is not a rule. It's just convenient for the voluminous supporting libraries.
<ryanprior>aecepoglu: thank you for sharing the package. I'd be happy to review it if you'd like, I've been doings lots of go packaging myself.
<elais>question: when doing `guix import elpa -a melpa marginalia` I receive an error because origin/master can't be found (marginalia uses the trendy "main" default branch name). Where should I raise the issue because its not really a bug so much as there are some repositories out there that don't use master. I noticed that in guix/git.scm we hardcode master as the default value when pulling from remote git repositories.
<ryanprior>aecepoglu: for MIT license what you want is "license:expat"
<ryanprior>Guix uses "expat" as a catchall for MIT, BSD-2, BSD-3, and various trivial variations.