<rekado_>We’re planning to give two talks there: one about reproducible bioinfo pipelines (using Guix for the “reproducible” part), and another one similar to what you and I presented in Vienna, but with a stronger focus on the number of bioinfo packages we offer.
<ng0>Guix has (so far) no problem with the company/product Guix, I suppose if there's already a name with something you want to offer and it's named exactly the same but acts in a different branch (whiskey vs software) it's not so difficult, right? it's not like some irish whiskey brand will come after me for using the same name. Though I'm considering a different name because … whiskey. bad marketing.
<bavier`>that a name overlaps with the same name applied to something completely different is not "marketing" per se
<ng0>I meant, bad choice of association, depending on how you value the other entity
<ng0>I need to look into how popular/known this brand is. Association with a whiskey brand is nothing I prefer
<jmd>ng0: Well, there is a trademark "Guix" registered in the software category. So far the trademark holder hasn't registered a complaint. Civodul's approach was to deal with that problem when it arises.
<lfam>So far, I don't know if I got to mesa or not. As of the latest core-updates, I don't have mesa built. When I try building on core-updates, it's by reconfiguring my headless GuixSD system on x86_64. So I miss lots of graphical packages
<thomassgn>Lately I've been having to figure out which packages provide certain binaries, like context which I found in texlive/tex.scm. Is there some way of searching through what the packages will output?
<civodul>efraim: well i guess that's an ok from lfam :-)
<AndChat306516>Guix on bootup is spawning a guile session saying: my-root: Inodes that were part of a corrupted orphan linked list found. my-root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. File system check on /dev/sda1 failed: spawning bourne-like repl