<eiro>also: from the doc: The sha256 checksum of the requested file. This is essential to ensure the source is not corrupted. Note that Guix works with base32 strings, hence the call to the base32 function.
<leoprikler>fwiw english still works, has the cookbook been translated yet?
<7GHAAGGRV>If I want to add a package, but I need to write two additional definitions cause it's dependencies don't exist in Guix, do I send each package separately in its own patch, or do I bundle the three commits into a single patch?
<eiro>guix download and guix hash while guix edit ... i have to revert things
<nckx>eiro: Both guix hash & guix download take an argument of the thing to [download and] hash; they don't look at the current Guix package set. Unless your edit left the ./pre-inst-env guix in a broken state, then you can just ‘git stash’, run guix, ‘git stash pop’. There should be no need to revert.
<eiro>damned! i screw the file up while using guix edit, i guess
<NieDzejkob>the build commands used. PKGBUILDs, Nix recipes (is that the word?)
<leoprikler>there should usually not be a need to reference them at all, but if you do have some very exotic setup, putting a link to an explanation directly in the comment is not a bad idea
<leoprikler>that said, the link should explain WHY some other distro does this, not what said distro does
<str1ngs>generally unless if it uses standard upstream build steps there is no need to mention the other distro. if though you need to do technical changes in order to make the package work, or with with guix specifically. just comment what those technical changes do. IMHO
<valignatev>Hey #guix, just noticed that ripgrep has landed with all its dependencies to upstream. This is super-awesome and encouraging, thanks a lot to all involved! I'm trying to package alacritty and ripgrep example should be super helpful for this.
<sneek>Welcome back valignatev, you have 1 message.
<apteryx>raghav-gururajan: yes, but this disables every tests. To disable a particular test, it depends of the test framework being used. Sometimes you can define a command line option to have them skipped, sometimes there's no other way than editing the source itself to delete or otherwise disable a given test.
<nckx>raghav-gururajan: It depends on the package and its build system. Often you add a phase (before 'check …) that either patches a file to remove a test from the list, or sets an environment variable to the same effect, or….
<nckx>There's no on-size-fits-all answer but many examples in gnu/packages.
<nckx>Great. Yes, there have been many installer fixes since 1.0.1 and everyone agrees there should be a new release in the next few weeks, but a system installed from 1.0.1 is still 100% fresh once you've pulled, reconfigured & upgraded.
<lekzikon>The documentation of "guile-build-system" says it installs the scheme files in the right place, and also the documentation. Is "documentation" texinfo documentation or just the README?
<lekzikon>I ask because I added texinfo documentation to the example library I packaged, guile-inutil, but "info guile-inutil" says there is no such thing.
<oriansj>Open call to all scheme developers: I need help with getting tests for how this: https://github.com/oriansj/mes-m2 is not guile; so that I can make it behave exactly like guile and we can use it as a drop in replacement for guile and make history.
<lekzikon>I discovered something nice about epiphany. If you are editing an HTML document locally and load it in epiphany, the document is reloaded automatically in epiphany everytime you save.
<lekzikon>This is useful when editing static websites.
<lekzikon>You can have the editor on the left side of the screen, the browser to the right, and see the changes load as you work.
<raghav-gururajan>Folks! If cmake-build-system throws this error "Error opening include file 'c-int-source-funcs.inc'". What is it mean?
<leoprikler>nckx: regarding ibus on GNOME, I plan on having ibus installed by default with my super gnome package (read: gnome + extras), but the way ibus works is currently not really documented well in Guix
<nckx>raghav-gururajan: I'm guessing this package is called libcoverart? It would mean that ./src is not in the include search path of the compiler. Adding -Isrc (that's an I as in Iovis) could help. We'd need more output to say more.
<raghav-gururajan>I thought I need older version because sushi which depends on it givers error "Could not generate cargs for libmusicbrainz".
<leoprikler>is there a way of handling this by default elsewhere, e.g. /etc/profile?
<nckx>Something like (string-append "CFLAGS=-I" (assoc-ref %build-inputs libcoverart) "/include") assuming that .inc file is actually installed. Otherwise you need to use (package-source libmusicbrainz) "/src" or something.
<nckx>leoprikler: Oh boy, you and your blasts from the pasts. I'd plain forgot about that hack.
<leoprikler>Heh, sorry. I really think ibus should work out of the box however 😉️
<leoprikler>Though I'd also accept a separate ibus-service-type
<nckx>raghav-gururajan: Well, you didn't give me more to work on than what I can duckduckgo. But OK, libmusicbrainz has that file too, it seems, as src/c-int-source-funcs.inc. Could you paste the full build output?