<ng0>when in a cmake based setup the files all are in /tmp/$out/build and the setup chdir's to /tmp/$out/name-version before copying the files and fails because the files are not in "." but in "../build", can this be fixed in advance? in CMakeLists.txt?
<dvc>nckx: this works: env -i GUILE_LOAD_COMPILED_PATH=/gnu/store/0fl8rpirg13jj4x5kfscjrb9smlhbvxi-profile/share/guile/site/2.0 ./pre-inst-env guix refresh --help
<nckx>Aha! Wonderful. So I'm lacking some environment goodies. That's at least a lead. Let's see if re-sourcing my profile... [nope]. Opening a new shell... [nope]. Re-installing the guix package which I never use... [laptop from hell].
<quigonjinn>roptat: well, there *should* be some difference in the environment variables, between the successful and failed tries. I would check the output of 'env' in a "--pure" environment with coreutils and go on by elimination
<nckx>dvc: I don't have anything GUILE_ set in my environment. That explains the symptoms. Now to find the cause. :-)
<nckx>(The cause is that I set up this environment on day 0 of my glorious Guix future and never looked back to re-do it properly, but whatever.)
<geemili>How do I get applications to run as background processes on startup?
<quigonjinn>roptat: you should look into the profile, what what paths that translates to, i think
<cbaines>geemili, do you mean as a system service, or for your user?
<Helius>I did the binary installation, and I am tring to build guix from git. I created the guix environment adding ad hoc packages and help2man is there. make tells me that WARNING: 'help2man' is missing on your system. but which help2man is /gnu/store/hs83kw23b37w57mdnjzsc9r5lifp3dsr-profile/bin/help2man and help2man —version is GNU help2man 1.47.4
<cbaines>Helius, maybe you need to ./configure again?
<Helius>cbaines: I did ./configure --localstatedir=/var
<cbaines>also, I think the main thing that using the git repository involves is building the guile object files, you might have the man pages anyway?
<cbaines>I have guix installed from guix (as in guix package -i guix), and ~/.config/guix/latest symlinked to a checkout of the guix repository
<Helius>cbaines: rekado helped me in setting up my guix but maybe I missed the same thing you are saying now about “~/.config/guix/latest symlinked to a checkout of the guix repository”
<cbaines>Helius, it would help to understand why you are building Guix from git?
<nckx>rekado: Thanks for the early Christmas present. Those graphs are awesome.
<alezost>Helius: ~/.config/guix/latest is the symlink to a guix source code created by "guix pull"; many developers don't use "guix pull" at all, and instead they make ~/.config/guix/latest a symlink to their guix git checkout, so they always use the latest code
<Helius>cbaines: to use the latest guix, thanks alezost
<Helius>i guess to use the latest guix I need to build it. running guix pull I had some trouble.
<cbaines>cool, so you are heading in the right direction
<cbaines>I normally run the following to build guix in the repository: guix environment --fallback --pure --container -N guix -- sh -c "make clean; ./bootstrap && ./configure --prefix=/ && make -j4"
<cbaines>sometimes, the following also works, if nothing has changed to much: guix environment --fallback --pure --container -N guix -- sh -c "make -j4"
<cbaines>I have aliases, so I don't type it out all the time!
<Helius>cbaines: thanks I will try it. in case it will compile do I need to shutdown the current guix-daemon and then run the new one ?
<Helius>How? Do I need to type also make install as root ?
<Helius>cbaines: in you command line guix environment --fallback --pure --container -N guix -- sh -c "make clean; ./bootstrap && ./configure --prefix=/ && make -j4”, why did you set the configure prefix and not the --localstatedir=/var ?
<cbaines>I think it may have been when I was trying to install the guix daemon from the repository, I think that might be the setting that gives the same behaviour as the binary installation, otherwise things end up in different places
<cbaines>Regardless, on foreign systems (e.g. I have a few Debian systems which I use Guix on) I would now just use the binary installation method
<rekado>davexunit: glad to hear that the new visualisation revealed a problem!
<rekado>davexunit: the radius size and the labels aren’t always optimal.
<rekado>actually, I’d be surprised if they were because I tested it with package graphs the size of R.
<rekado>I really wanted to make this a little smarter but … yeah. So instead of having it rot away in a local branch waiting for me to get around to improving it I thought I’d rather push it now.
<Helius>so I had to add some —ad-hoc the the basic guix environment posted by cbaines $ guix environment --fallback --pure --container -N guix --ad-hoc guile-cairo guile-charting guile-rsvg -- sh -c "make clean; ./bootstrap && ./configure --localstatedir=/var && make -j4”
<geemili>Is it possible to install a system wide font?
<geemili>I keep getting little boxes from missing glyphs
<SovereignBleak>I was just about to pull the trigger on testing a Ruby development environment with nginx and postgres with NixOS but then remembered that GuixSD was a thing and that it much of it was written in a language similar to the language used to make my beloved Emacs. Is GuixSD ready for that kind of task?
<SovereignBleak>Or should I just stick with making him an environment built on NixOS?
<rekado>I’m running a simple webserver with nginx on GuixSD.
<rekado>I’m not using postgres and I don’t know off-hand if we have a convenient abstraction for configuring and starting postgres.
<rekado>geemili: make sure you install a font that contains the missing glyphs, install it into your profile, and run fc-cache to update the font cache.
<rekado>geemili: usually you don’t need to install packages into the global system profile
<rekado>(you can do that if you’re using GuixSD by adding packages to the “packages” field of your /etc/config.scm)
<cbaines>SovereignBleak, I've been doing pretty well with doing Ruby development with Guix
<SovereignBleak>cbaines: Oh this is good news. Do you have whatever passes for a GuixSD configuration.nix on github somewhere?
<cbaines>Its not particularly pretty, but it works more or less
<cbaines>I really need to update it, as I've been making quite a few improvements since I did the original implementation
<SovereignBleak>Anything is better than the fog of nothing I'm dealing with right now. :-)
<cbaines>I was going for a particular set of possibly unusual requirements, e.g. using environment variables to affect package sources, so the gds/systems/end-to-end-test.scm file ended up being a real mess
<cbaines>I've been working on building system containers, but that might not be what you want for development
<cbaines>Easy development is something that I'm yet to really get a handle on, some of the conventions in rails (where it expects the rails root to be mutable) and trying to fight with bundler don't really go well with Nix and Guix
<SovereignBleak>He'll also be doing website hosting for clients (potentially). This is all just testing other methods of hosting and deployment since he's been using Ubuntu and it's been dependency Hell for him.
<SovereignBleak>rekado: I'd also be interested in seeing your Guix configurations for my own education, if those are around.
<rekado>SovereignBleak: my nginx config is messy :-/
<rekado>SovereignBleak: our config abstractions need to get an “escape hatch” to allow us to add config snippets for things that our config language doesn’t cover.
<rekado>SovereignBleak: at the moment that’s not the case, so I’m just using an ugly external configuration file and tell the nginx service to use that.