<roptat>so close! I again need to change my version of the ant-build-system, so rebuilding the java world again before I can test the build of my package
<nckx>aidenholmes: That's handled by nix-service-type which also runs the daemon but I agree, if you want Nix on Guix install it the Nix way. I can't imagine the Nix package & service in Guix being well-tested or -loved.
<nckx>Veera: A work-around if you don't have tens or hundreds of files failing: ‘curl -LO <the URL>’, or ‘wget <the URL>’; then ‘guix download <the local file>’ and rm <the local file>. Both curl and wget can resume downloads although I'm not sure if they do so by default.
<rlemmon>I am trying to install guix on a nixos machine using the install shell from the guix website. All goes well until the script tries to install the guix-daemon service. It cannot install it in /etc/systemd/system and so the daemon cannot be started. Has anyone come across this problem ? I thought the /etc filesystem was writeable as that is where e.g. configuration.nix lives which I regularly modify.
<tsmish>Hi #guix. I'm trying to package a program, which requires freetype. It includes <ft2build.h>, but this file doesn't exist on guix system. It exists as <freetype2/ft2build.h> but that file assumes that freetype headers are in <freetype/*>, not in <freetype2/freetype/*>. Still, there are packages depending on freetype which somehow work. So how do they do that?
<DamienCassou>just to be sure, when calling the `package` function, should the next line have its opening parenthesis aligned under the "a" of `(package` or the "p"?
<nckx>rlemmon: If I had to guess I'd say /etc is writable but /etc/systemd or /etc/systemd/system links into the store, which isn't.
<civodul>anyway, no big deal, but sorry for overlooking it
<DamienCassou>in my next patch on this, should I get it fixed or should current indentation be kept?
<DamienCassou>I will deactivate aggressive indent in guix code because indentation seems broken everywhere
<civodul>either way is fine, but it's probably best to have indentation fixup in its own patch
<civodul>perhaps you need emacs-guix to get indentation correct, but this is surprising
<civodul>i think most special rules are in .dir-locals.el
<rekado>janneke: would you like us to build the wip-hurd branch on ci.guix.gnu.org?
<DamienCassou>civodul: I now think that my configuration is correct. The problem is that many package definitions are broken according to it. I usually have aggressive indent that re-indents everything I touch. This is problematic because it tends to change many lines everywhere because they have a "broken" indentation
<civodul>DamienCassou: ah yes, you should disable that
<civodul>obviously there are packages with slightly different indentation here and there
<civodul>(also because the rules changed over time i guess :-))
<DamienCassou>I suggest doing a pass on every file in the project so we have a correct indentation everywhere
<civodul>i think it's best to "fix" things incrementally
<civodul>otherwise that just makes "git blame" harder to use
<NieDzejkob>termite pulls in xdg-utils, on core-updates qt does too...
<guix-vits>NieDzejkob: just the BugReport i'd posted above is old, and neither wxwidgets, nor audacity push it yet.
<guix-vits>So patch with xdg-utils appended to `(p.-inputs` can pass?
<nckx>guix-vits: No. Don't propagate inputs, patch them. See ‘termite’ for an example. Both calls to xdg-open are in src/unix/utilsx11.cpp. We can probably get away with simply making ‘path’ a hard-coded string in both cases.
<nckx>Oh, not even that. Patch ‘wxExecute(xdg_open’ to ‘wxExecute("/gnu/store/…’
<nckx>guix-vits: My ‘let's see if this works’ patch just worked, so I can push it if you wouldn't have the time. It's a good simple learning opportunity though.
<guix-vits>nckx: i've a time, but if the patch is already there, i'm prefer a link to it to study. As i'm uderstood the 'termite', one uses (lambda and (substitute* to use `(input`'s xdg-open, which is not installed, but available for the package (as which executed in build env.).
<anadon>civodul: Can you see the attached file from 40043's first email?
<nckx>guix-vits: OK, I'll post it. Compiling it now to make sure. Your understanding of what termite does is correct: ‘guix environment --pure --ad-hoc termite’ won't be polluted with xdg-friends.
<allana>Hi, I have seen some references in the guix cookbook to "macbook". Is anyone running guixsd on mac hardware? I recognize that this is hardware requiring nonfree software/firmware and this against what many of us stand for, but I thought it would be safe ot ask about since it is in the cookbook.
<vagrantc>well, i managed to boot a 5.5.9 linux-libre + one patch from linux-next to enable pinebook-pro ... but when i went to add a second patch, it now fails to build ... and when i revert, the old version doesn't work anymore either
<lfam>But it doesn't help when big corporations create free software tools and GNU activists look down on those tools just because of where they came from. Even though the people actually making the tools are die-hard FOSS activists
<jackhill>I think the important thing is to have a diversity of interests in a project. Some large entities, some small ones, some individual hobbiests. It is a problem when too few entities control a project and their motiviations are not in aligned with mine
<jackhill>bkuhn's talk about IoT at LibrePlanet touched on some of this: e.g. the biggest funders of Linux are interested in cloud workloads which can but doesn't nessisarily help hackers who want to use Linux on their oven. It is up to us to speak for the Linux-based oven firmware users.
<lfam>I didn't see that one jackhill. Sounds right up my alley!
<jackhill>lfam: videos will be up soon I'm sure :)
<lfam>I'm my opinion, it's true that "desktop" linux is not becoming a more mainstream use case, and is even beginning to atrophy
<lfam>I don't see any activity towards free wifi drivers after 802.11n
<janneke>mbakke: about the patches: ah, I see; yes, i'll update them
<lfam>You can't use libreoffice Blackbeard? The file formats should be compatible
<janneke>mbakke: i just found that wip-hurd fails to build on ci.guix.info -- i removed a glibc hurd patch that i was sure wasn't used; so that needs a fix/rewrite too
<nckx>civodul: If you agree, I've replaced GuixSD with Guix System in all website/posts. I don't think there's any value for readers in keeping the old name alive or tediously saying ‘(formerly GuixSD)’ everywhere in these. The confusion hurts us and splits search results.
<sirgazil>Or leave them as they are. It's part of Guix history.
<sirgazil>And that was the name at the time of those posts.
<nckx>That's why they should mention the new name, so it's obvious they're outdated.
<nckx>Seems like '0,/GS/s//GS (f GSD)/' should do what I want.
<nckx>I'll use ‘GuixSD (now Guix System)’ in links to immutable things like talks.
<nckx>lfam: Does systemd start root's user services (~root/.config/systemd) at boot?
<lfam>nckx: It depends how you set up systemd and loginctl (users registered as "lingering" have their services started at boot). But I think it's better to bake it into configuration.nix as somebody else suggested
<lfam>I don't know if root in particular lingers by default. Unprivileged users do not
<nckx>I'd find it strange if root's were treated magically by default but this is systemd we're talking about.
<roptat>or it could be even simpler: add a paragraph at the beginning "this article uses the term "Guix SD" which is the old name of the Guix System. We have preserved this name in the old blog post" or something