<ng0>on "it's probably easy" as famous last words: firefox doesn't look that difficult either.. only some changes to icecat and some understanding needed which can only be found through grep, debug and coffee.
<roelj>but then when installing perl-b-hooks-endofscope, it still tries to download that dependency, and thus fails..
<rekado>civodul: I don't have a libreboot machine --- yet. I'm testing a new flasher from a completely free hardware design (even the microcontroller's design itself is under GPL), developed by some FSFE fellows in Berlin.
<rekado>the flasher worked fine on some X200 machines, but failed on my X200S.
<rekado>hopefully we can flash my X200S on Saturday after fixing the remaining issues.
<civodul>wingo: i think it's just the "skip incompatible .go files" thing
<civodul>"Guix has been available for a range of GNU distributions for several years. It allows application developers to build against a series of stable platforms (known as runtimes), as well as avoid bundling libraries directly within their applications."
<civodul>"A growing range of applications are already available in Guix, including LibreOffice, the GIMP, InkScape, MyPaint, Darktable, and a large number of stock GNOME applications."
<Kooda>ACTION is currently installing GuixSD on his laptop. :D
<civodul>Kooda: it'd be interesting to learn more about their perception
<davexunit>we can promote guix and market it without looking like that Habitat website that is 100% buzzwords
<Kooda>civodul: it seems more like a feeling than anything else
<wingo>civodul: i'm down with the utopia :) i just think people never made decisions rationally in the past, no reason to expect it in the future, and no reason for guix to shame story-telling; we need stories too :)
<davexunit>there are stories to tell for desktop users, server admins, software developers, etc.
<davexunit>might be nice to highlight that prominently on the home page
<ng0>sorry to interupt this discussion, just wanted to say i dropped a broken, untested, firefox wip in a thread, to ask an example case for when an in-file substitute gets too long and a .patch should be used
<ng0>140+ lines of substitute to enable system harphbuzz and graphite2.
<davexunit>ng0: just fyi, we cannot include a package named "firefox" in Guix without violating Mozilla's trademark
<pksadiq>ng0: Hm.. but it should have sane defaults. I love Debian GNU/Linux for this
<ng0>my knowledge about the addons is not so good, but it is possible to disable the checking. if it is built only with our store plugins (guix package -i icewhatever-baseextensions) and then only install extensions through guix and not firefox, that would be something to consider.
<ng0>ACTION compile icecat with the system harfbuzz+graphite2 patch
<ng0>as i expected, things changed between 38.8 and 45.0 .. but it should be doable with some fixes in the patch
<paroneayea>davexunit: civodul: it looks like upgrading postgresql means needing to keep around the older postgresql binary. What do you think of keeping the "prior version" (or last few versions) of postgresql around?
<davexunit>so looks like you have the right idea, then!
<Kooda>Sorry to interrupt… is there a way to specify a default console (and/or X) keymap in the system configuration file?
<ng0>I'll be brave and build firefox/aurora now, to get some debugging output
<ozzloy>guix marketing blurb: guix thinks outside the box in its search for the holy grail, understanding that there is neither a magic bullet or a slam dunk method, so it rolls with the punches and lets the chips fall where they may while seeing the glass as half full. use it today, it's a no-brainer!"
<ng0>here's what I think, leaving aside names and tm's: firefox-esr as a base for torbrowser, the base firefox being first removed of any access to non-free extensions and plugins, and later to remove/alter the plugin checking and import addons which are possible to import (license) into for example webbrowser-extensions.scm
<ozzloy>what needs to happen for the name to change?
<paroneayea>ozzloy: that's a huuuuuge conversation to even consider
<efraim>if you meant firefox there's a couple of flags you can set during configure time
<paroneayea>I also kind of doubt Guix will change as a name. But maybe the pronunciation should be more visible on the website.
<ng0>hm... i think this is getting to the point where my main focus is falling behind. I can fix up a basic package which has all languages, the rest someone else can take on. I'll decide when I'll get it all to build.
<ng0>how can "guix download" work on a list of files? just append them all after the command, or can it get an input file?
<efraim>if you need more than 1 you can add the others as inputs and stick them in the right spot or apply as a patch as an added phase
<ng0>this one game with the many data-sources is an good example, but i feel like this can be handled differently.
<ng0>only twice if i686 packages differ in checksums
<ng0>why would languages differ. I'd say it's only a structure thing
<ng0>I'm still learning, so something in a package like "for i in (list of languages) do wget uri://base.name.org/folder/name/version/arch/iso-lang/file.tar.bz2 , then unpack and use in the package" ... well the closest which I get to this currently is this one big game with mapping
<davexunit>weird. running the same version of guix on two machines. one from a git checkout, the other as a package I installed. the first didn't need to graft a package I was building, but the second does.
<davexunit>building the package without grafts on the second yields the same hash for the store item
<davexunit>there *must* be a difference, but I'm pretty stumped.
<davexunit>the second guix machine receives substitutes from the first
<rekado>about the name: people here at the institute seem to like it once they hear me pronounce it.
<rekado>most often they try too pronounce it as "goo-iks", which sounds awkward