<h4ppy>can anyone help me with fontconfig? I have installed it in several different manners (did guix system reconfigure including it, normal guix package -i) yet I cannot open it. When in terminal, it says that the command "fontconfig" doesnt exist
<jlicht>If it is the one in i3, I use `font pango:DejaVu Sans Mono 8`, which never gave me trouble
<h4ppy>jlicht: I mean supposedly I can change the font for the terminal emulator I'm using, which is a matter of the terminal editor config. but then how do I change the fonts of i3 and i3status/i3bar? is it then only a matter of i3 (and then all other programs in which I want to change the font?)
<h4ppy>sorry for the noob question, but what is the difference between the two, and where can I access the headers?
<Sleep_Walker>civodul: this allows it to not implement any configuration parser and make code smaller, suckless.org people focus on creating minimalistic software which is easy to read, modify and proof it's correct
<h4ppy>atw: I think so, actually. I mean I can kind of figure that run-time might be associated with a configuration file that is read, versus a "hard-coded" compile configuration that can only be altered upon re-compile.
<h4ppy>but if it is that easy to edit suckless programs by editing the headers, I dont exactly know where to look for them
<ng0>efraim: icecat with rust+cargo 1.24.0 compiled, no build errors, still starts up normally
<verisimilitude>I downloaded GCC 7.2.0 recently, but it doesn't seem to be a GCC that supports Ada; which package should I download to get a GCC with Ada support?
<atw>h4ppy: my workflow for that would be to git clone the suckless program, make changes, commit them, use git to make patches out of my commit(s), and then do as Sleep_Walker did in their link: make a package definition that inherits from the suckless program (in their example, dwm) and add your patches to that. You can find Sleep_Walker's patches here: https://github.com/sleep-walker/guix-extra/tree/master/gnu/packages/patches
<ng0>h4ppy: in case they are trivial changes, you can use "substitute*" in the package definition
<ng0>for anything more complex, track the patches in a git to rebase on new releases
<atw>another approach: git clone the suckless program, make changes, commit them, push them to your own publicly accessible repo, then make a package definition that inherits from e.g. dwm and specifies the origin to be your publicly accessible git repo
<ng0>I generally commit unpacked tarballs (of for example suckless software) into a git, make an initial commit, and then work my changes into it if I need it
<ng0>in rare cases you could make a releases and use the file locally or remote
<georges-duperon>civodul: guix pull --commit=xyz -p ./profile && export PATH="$PWD/profile:$PATH" && guix system vm config.scm # how does it know to use e.g. emacs version as described in package recipes version xyz ?
<civodul>georges-duperon: each guix instance comes with its own package set, so if you run 'guix' from commit xyz, it will use the 'emacs' package as defined in commit xyz