<littleme[m]>👻oh yeah, and you became a small part of dear osx, rm -rf money_pride_control
<littleme[m]>and ifconfig lots of unknow interface 🐑 hope nix at osx save your soul.
<littleme[m]>Maybe you will feel pride about yourself that you can afford double even tripple price to use a machine that just work like others. 👻 dear, and the software actually suck if there is no electron-tech
<littleme[m]>unless you choice M1, it's not cheap, at least it show the design of good power manage to CPU.
<davidl_>what is required for a package's info file to be installed correctly when you make a package using the gnu-build-system?
<janneke>jpoiret, civodul: i managed to build "hello" natively!
<futurile>davidl_: are you sure it's not being 'installed' (copied to the right location), versus your profile not finding it? AFAIK if the underlying 'make install' command works then the docs/info should be installed correctly
<janneke>civodul: you asked about all the new failing coreutils tests on the hurd and debian
<janneke>i didn't find patches or anything before, but i just found how they do it
<civodul>to some extent it's good because it avoids discovering problems down the road
<civodul>OTOH, they're sometimes too picky, like testing things that aren't mandated by the interfaces
<janneke>civodul: there are still 6 gnulib tests that fail (one less), but no, all new failures are coreutils' own tests
<janneke>civodul: i haven't looked into the test suite, i would hope that they have basic tests, and then picky ones
<janneke>ACTION wonders if such feedback ever reaches upstream: your tests don't work for us, we turn them off
<davidl_>futurile: basically, Im writing a Makefile right now for one of my own projects, trying to make things work as smoothly as possible with Guix' gnu-build-system. I am new to using make though, so Im not sure how .info files are normally handled.
<davidl_>I have a build directory where I put all files, like build/bin, build/share/project, build/share/info, I just wonder how things are handled with info files so I can avoid trial and error with it.
<lilyp>unless you have a good reason not to, I'd suggest using autotools
<janneke>ACTION pushes a (their) wip-hurd branch with the two pending patch sets (that need some cosmetic changes) and the to-be-sent commencement one, and some goodies
<janneke>yeah, it can get tricky if you don't align
<janneke>i usually keep adding squash! commits until we agree to squash them all, and reset
<davidl_>lilyp: ok thanks for the suggestion. My projects are not C. They are mainly bash and python projects, but still for at least Bash it might be useful. I just want to make it into an easy and standard build process.
<ChocolettePalett>You could look how they do it in other projects, but I can't remember any project that uses info files
<jpoiret>ChocolettePalett: do you mean info manuals?
<jpoiret>lots of projects use info manuals, I suggest checking out your `info` do have a look at some examples
<jpoiret>they're less popular then man pages for sure though
<lilyp>davidl_ for python, prefer the pep-whatever build systems, there are some useful ones in guix
<lilyp>(assuming python is the only language in the repo)
<dthompson>jpoiret: I totally missed your question yesterday. I was having issues where a guix pack binary wasn't running correctly because it couldn't find glibc locales. I was able to solve this problem by using a wrapper script that set GUIX_LOCPATH appropriately.
<jpoiret>petition to add forceinbodyfrom=true to our git config
<spacecadet[m]>Hello guix, I'm in the unfortunate situation of needing to run guix shell inside a guix system vm. Even if I wanted to give the vm r/w access to the store (I wouldn't) I don't think that's possible to do safely. Does anyone know a workaround here?
<civodul>spacecadet[m]: hi! you could use a full-blown VM image ("guix system image -t qcow2"), and there you could run guix-daemon and all
<davidl_>ChocolettePalett: me neither, other than that I know that with guix I can use info guix :-) I checked it out but didn't find it informative. I eventually just looked at the gnu-build-system in the guix source, and I think it'll work out fine if I just have a make install phase that installs some info files to /usr/local/share/info, however, it remains to be seen! I will just have to do trial and error soon.
<lilyp>whatever you do, just make sure to honour $prefix and you ought to be fine
<davidl_>yeah seems like it. Ill probably do a preliminary regular configure and Makefile scripts before sswitching to configure.ac and Makefile.am
<VesselWave>Hi! How to send a guix patch with mu4e the most efficient way?
<patrickt>Hello, sorry if this was already asked and addressed (that last few days have been pretty draining). Trying to set up Guix on a new system but the 1.4.0 installer keeps failing with 3 different internet connections. I ran guix pull in command line, which reported back guix pull: error: Git error: the SSL cetificate is invalid. Help is immensely appreciated. I am also eager to help make the installer more streamlined (would be nice if it could
<patrickt>automate more of the disk partitioning stuff)
<patrickt>By failing, I mean, it says the substitutes servers are inaccessible
<VesselWave>TheSkylarverncc[: Sorry I haven't really used guix home
<VesselWave>TheSkylarverncc[: plain-file reqiures string, computed-file requires gexp. I don't know how to make gexp that outputs string
<jpoiret>i wonder why the error message doesn't have the proper location though
<ngz>sneek later tell rekado I kinda start to understand the hyphenation issue we're facing in modular TeX Live. It seems that texlive-babel must be among the TEXINPUTS when latex format is generated. IOW texlive-babel must an input for texlive-latex-base, which creates a circular dependency.
<janneke>jpoiret: shouldn't these be (libc-for-target)?
<jpoiret>civodul: ???? now that abracadabra trick i really don't understand
<mirai>Any gexperts know how to read the built (mixed-text-file ...) from within the same source? I'd like to write a guix test that checks if the serializing procedure really writes the correct output <https://paste.centos.org/view/6093867e>
<jpoiret>how does adding some random piece of syntax that you don't use in the end add the location?
<mirai>I'd like to essentially automate ",use (guix) ,build (mixed-text-file ...)" ; "cat <the resulting path>"
<civodul>jpoiret: the piece of syntax we introduce inherits source location from the original form
<civodul>we don't actually care about what the content of that syntax object, we only care about its location