<CaptainDrewBoy>Hi! I ended up going with the guided install (didn't use it bc at first it wasn't working). I installed i3 and it automatically grabed the st terminal. I don't mind this at all. But how do I apply patches to the st that guix installed? I know that guix sd doesn't take kindly to make install, so installing it separately is a no-go (I imagine).
<podiki[m]>CaptainDrewBoy: I don't know st, but take a look at "package transformations" in the manual
<podiki[m]>you can add patches to be used when building
<podiki[m]>otherwise, perhaps taking the package definition and making your own version
<geex3>i would think most st users apply patches so it should be easy. but i don't think it is
<geex3>I need to define a simple (openvpn client) service that runs "openvpn /etc/openvpn/client.conf" command instead of having the client configuration in the configuration.scm - (some of the other services depend on the virtual network to be in place to listen on that interface, so nm-applet is not ideal, and the vpn config may change between guix system reconfigures)
<raghavgururajan>geex3: I don't think its a good idea, as the advantage of guix is declarative+reprducible system management.
<geex3>well currently users need to run 'sudo openvpn client.conf'
<geex3>for now i will stick with 'sudo nmcli connection import type openvpn file /path/to/file' but looking for way to have it at the herd level with a conf file -- will share if i end up having any luck
<singpolyma>Hello everyone :) On today's adventure, I run: ./pre-inst-env guix lint <my-new-package> from inside guix environment guix and am told: ls: cannot access '/usr/local/var/guix/daemon-socket/socket': No such file or directory
<singpolyma>Any ideas what I should do? Is there a ./configure switch I need or something?
<iskarian>singpolyma, yes, you must do `./configure --localstatedir=/var'
<singpolyma>When I submit a patch-series for new packages, should it always be one commit per package, even if there are say two very closely related ones (like a package and a helper package only it depends on) ?
<iskarian>Better to err on the side of one-commit-per-patckage
<nckx>(Hm, I guess using both --system and --target *would* be unambiguous, but in any case it's not implemented :)
<efraim>the cmake packages FTBFS intermittently on aarch64 on core-updates-frozen. Part of me wants to change the 'check phase to (or (assoc-ref %standard-phases 'check) (apply (assoc-ref %standard-phases 'check) #:parallel-tests? #f)) since that always seems to take care of it
<guerrilla>So, question: How do I list what packages are installed in the base system? guix package -I as root doesn't list anything. I looked through the 'guix system' man and didn't see anything relevant there either.
<nckx>I guess I'd use something like ‘guix size $(realpath /run/current-system)’, guerrilla.
<nckx>Aside, note that root is just another user, not ‘the system’. That matters or you'll encounter misexpectations.
<guerrilla>nckx: Thanks. Yeah, I suspected the latter, just was the best I could think of for a first try :)
<nckx>It's not a great answer but I don't know if there's a way to get a more package-oriented output.
<nckx>Well, that's the catch with the above command, it uses the (correct but strict) Guix definition of ‘installed’ and won't list any packages that are used only by services but not added to your system profile. elogind is there (presumably) to provide loginctl, but e.g. xorg-server isn't.
<maximed>possibly 'patch-shebang' will take care of patching the shebang
<maximed>(I'm not familiar with xinitrc --- is it a configuration file to be modified by the user? If so, maybe keep it /bin/sh, such that the configuration file doesn't become invalid after a "guix gc")
<jpoiret>i'll put the script inside the scheme code so i'll put the right shebang manually
<jpoiret>it's the code responsible for setting up the environment for an X session
<maximed>mfg: what is the value of $C_INCLUDE_PATH?
<maximed>If it is undefined, maybe clang-toolchain and gcc-toolchain weren't in your profile previously, so C_INCLUDE_PATH is unset, so you need to restart to have these environment variables defined
<mfg>nckx, maximed: Ah, running clang from the command line works. I'm using emacs wich clangd so i guess there is a difference leading to that "error"
<permcu>Hi everyone, is there a way to add local files/ folders to the operating-system definition so that they are added on system creation? I would like to use this to create a ready to run vm image.
<iskarian>It's funny that you bring that up, recently I was looking at ways to properly split up clang, like backporting their use of GnuInstallDirs
<mfg>well at least for the builtin headers i think the relative path in clangd would have to be substituted with the correct store path. The docs seem to imply that these are too essential and therefore hardcoded... Every other header (especially those in say CPLUS_INCLUDE_PATH) just work as they should
<nckx>iskarian: There isn't yet a concept of ‘low priority jobs’ but it could be added by someone who needs it 😉
<nckx>kraai: I meant the opposite (actually package @7 for Guix so elm-test is happy), but both are valid. If you think elm-test is being too pedantic, it could work. Python packages do that a lot.
<iskarian>mfg, perhaps, though I'd prefer a more general fix. clang takes a long time to build and has a lot of dependents, so it would probably be easier to edit what is invoking clangd to use -internal-isystem or something
<iskarian>until the underlying issue is fixed, that is.
<mfg>makes sense. In my case it gets invoked by emacs lsp-mode. But i'm not using the guix package - i'm using spacemacs.
<geex3>can i test build and start a service from .scm file, without reconfiguring system? like ad-hoc or something? (for developing/testing new service)
<mfg>So one workaround is to add the correct store path to an arbitrary clang++ invocation and use bear to generate a compile_commands.json from that. Now clangd also picks up the stddef header
<mfg>but this has to be done for every project so it's working but not nice :D
<jpoiret>also on a side question: is there any specific reason guix uses debbugs instead of more *ahem* modern git platforms? (gnu policy, impractical, etc...)
<excalamus>I'm writing up some notes about a recent build I made. To get the needed modules, I'm curious the "right" way to find them. Some are suggested by guix build. Sometimes, the error message is vague, like "/home/ahab/test.scm:22:14: error: pypi-uri: unbound variable". I solved this by cop