<davexunit>I'm hesitant to ship C code with my primarily Guile code because it makes it that much harder for others to use my stuff, but I feel like I have no other good option.
<bavier>davexunit: what about a C extension would make it harder for others to use? Just curious, as I've little experience with that part of Guile, though I had always thought C extensions were one of its features.
<davexunit>it's no longer pure guile, so now they need a C compiler to build things.
<bavier>many take such a thing for granted I suppose
<next_step>we had a nice chat yesterday about ARM, libreboot and guix
<lfam>I'm just trying to understand it. It doesn't seem to be a hash collision. So is it a package name collision?
<DusXMT>lfam: lib/perl5/5.16.1/x86_64-linux/perllocal.pod is in both git-2.4.3 and irssi-0.8.15, and when creating links for the packages into your profile, it needs to pick one of the two to put it in
<mark_weaver>lfam: building a profile involves producing a union of all the /gnu/store directories in the profile
<mark_weaver>and sometimes two store directories have the same file in the same relative subdirectory
<alezost>lfam: it means that both "irssi" and "git" have a file with the same name (lib/perl5/5.16.1/x86_64-linux/perllocal.pod)
<mark_weaver>a simpler example of a collision that might occur is this: if you install both 'emacs' and 'emacs-no-x', they both contain bin/emacs
<mark_weaver>so if you try to install both of those in the same profile, then the question arises: which one should be put in ~/.guix-profile/bin/emacs ?
<mark_weaver>and in this case, the question is, which file should be put in ~/.guix-profile/lib/perl5/5.16.1/x86_64-linux/perllocal.pod