<marusich>I just looked, myself; maybe it isn't so helpful
<marusich>Looks like that's for constructing a wrapper script, so it adds stuff to the environment using shell syntax. I'm sure somebody somewhere in the packages has already added stuff to an env variable; maybe looking for usages of "setenv" will help
<ng0>this has some erros, but something like it will work
<ng0>is this meta-games, trying to package games for months? :D
<marusich>Assuming that the rest of the build will see that value for PKG_CONFIG_PATH which you set, it seems reasonable...I wonder why the build system you're using isn't automatically setting up PKG_CONFIG_PATH correctly in your case, though.
<bldtg>jmd: hmm. I must not understand how it works then. when I add my path and then do something with guix package or guix build, I get "warning: failed to load '(package-name)" and "ERROR: no code for module (package-name)
<jmd>bldtg: I've never tried it. So I'm afraid I don't know.
<gwonder>HI everyone, I'm looking for some support with a newly installed GuixSD installation. I've installed with the gnome desktop options, and I can boot but I can't figure out how to get NetworkManager running (at all, during boot or after) - from what I've read it may be something to do with disabling wicd somehow and enabling NetworkManager specifically
<gwonder>So I'm looking for advice on how I modify this file to get NetworkManager running, and when I make changes to this file are they enabled on reboot or do I have to do something to enable changes?
<gwonder>I can get networking using dhclient -v eno1
<gwonder>this is my updated config.scm ( http://paste.lisp.org/display/335229 ), however it returns "/etc/config.scm:10:2: In procedure #<procedure 39537c0 ()>: /etc/config.scm:10:2: In procedure module-lookup: Unbound variable: remove"
<mange>The `remove' method comes from the (srfi srfi-1) module, so you could add that to the use-modules form up the top.
<vtomole>mange: my config file is exactly like his, but my error is "In ice-9/boot-9.scm: 160:13 [catch #t #<catch-closure 1b1020>..]
<roptat>hi, I'm trying to make an ocaml-build-system. It's currently working and I added around 100 ocaml packages. Should I make a separate patch for each of them, or add them in a single patch?
<gwonder>(I don't actually care about wpa_supplicant, but adding 'networking' to the modules at the top seems to force it as a requirement. Without 'networking' loaded at the top it reports network-manager-service as an unbound module, so I think it's required
<mange>You definitely need 'networking' in the service-modules section up the top. The network-manager service should then provide networking for wpa-supplicant. At what point is it complaining about that?
<mange>vtomole: Your problem is because you don't have 'networking' in the service-modules section up the top.
<roptat>I think you should add (service wpa-supplicant-service-type) to the list of services in your config.scm
<gwonder>thanks mange and roptat I'm having a look now
<vtomole>mange: the docs on the manual are oudated then... If i wanted to fix them, how would i do it?
<mange>vtomole: I think they're under the doc/ folder in the guix source tree. What is out of date in the docs?
<gwonder>I think I'm almost there, I'm getting "unbound variable wpa-supplicant-type" and from my previous errors that tells me I probably need to load another module at the top of the file - does anyone know what I need to load, or where to find the documentation for what I'm asking?
<mange>vtomole: There are there example configurations on that page and all of them look fine. The first one, which uses 'networking' actually makes use of it, the other two don't reference anything from 'networking' so they don't include it in the use-service-modules form.
<rekado>vtomole: we need more context to assist you
<ng0>I think I can just pick the solution to copy the files there and not care about broken symlinks as they disapear
<ng0>this 0ad build is powered by ES technology: everything sucks
<joshuaBPMan_>Hello, I'm running guixSD (obviously). I can login to a virtual console, but I cannot start gnome. I'm getting two main errors. gnome-session-binary cannot parse desktop file xscreensaver.desktop and gnome-keyring-daemon couldn't access control socket /run/user/0/keyring/control no such file.
<orbea>Hi, I maintain guix for slackare at slackbuilds.org and I just noticed this which I overlooked before. http://dpaste.com/35PJN4Y Its not a good practice to download stuff during the build process, is there anyway to disable this?
<lfam>orbea: Try searching the guix-devel and bug-guix archives for clarification. It works for me, too. I think the idea is that it works at run-time, but we don't want to depend on those things while building. But I'm not sure :)
<lfam>bldtg: Probably the module path exported by your custom package definitions doesn't match the filesystem path underneath GUIX_PACKAGE_PATH
<lfam>The module path is exported by (define-module)
<efraim>sneek: later tell ludo I'm going to write a more indepth "help with aarch64 port" post later, but as far as I can tell, the crux of my problem can be seen in this diff between stage1 and stage2 of gcc-final, in the libXXX config.log-s https://i.imgur.com/5LP41Il.jpg , if you want to take a look at it first
<lfam>ctrl+alt+fn-key switches TTYs for me on the Debian system I'm using. I don't remember if it's different on GuixSD, or if QEMU complicates it
<lfam>I'm not sure of a good way to debug this. The crude thing I'd try is to reproduce the failed login and then kill the x server from another TTY. Then I'd go back to the first TTY and read the console output
<lfam>Ideally everything started by shepherd would get stdout and stderr redirected somewhere
<thomasd>yes, in a similar vein, I just managed to take a screenshot :D
<thomasd>something about "unable to connect to D-Bus: /gnu/store/.../dbus-launch terminated abnormally with the following error: No protocol specified
<lfam>Does anyone have an example of how to set up the default log rotation? The example in 126.96.36.199 Log Rotation results in "Wrong number of arguments to #<procedure mcron-service (jobs #:optional mcron)>"