<fhmgufs>Hello, I'm almost ready with GNU XaoS now, it took a very long time (it's my first attempt :) ). But there is still one problem: the build process works fine, but the installation doesn't work because of some missing .mo-files for i18n. Is that related to the missing locales message I see every time I invoke guix? I followed the instructions in the manual to install the locales.
***necronian_ is now known as necronian
<fps>sneek: ask fhmgufs later: maybe add intltool to the native inputs? no idea. just guessing
<fps>sneek: later ask fhmgufs: maybe add intltool to the native inputs? no idea. just guessing
<pirfle>Hello, does anybody know, which is the best solution for running guix as the default system on the Raspberry Pi 2 B? Should I install the basic rasbian system (e. g. with https://github.com/debian-pi/raspbian-ua-netinst/) or just install firmware and so on and then guix from another machine?
<jmd>pirfle: Are you trying to install Guix (the system) or Guix (the package manager) ?
<fhmgufs>Yes, and I have a question: My package needs to know the localedir ($GUIX_LOCPATH). I pass the configure option --localedir=$GUIX_LOCPATH, but then the config script fails. If I run it outside from guix it works.
<fhmgufs>Back to my problem: I tried it with glibc-utf8-locales as an input and without --localedir=$GUIX_LOCPATH (that was really silly). Now it works, but only until it reaches the locales which aren't included in that package. Do I really have to add the huge package glibc-locales to the inputs or is there another option?
<alezost>swedebugia: but if you are going to send a patch to guix-devel, you'll need to work guix from git eventually
<swedebugia>alezost: trying your paste. I got past the error and it is working on trying to find a substitute now... --no-substitutes might be wise to add to skip that step
<efraim>fhmgufs: sounds like you might need all the locales then
<efraim>hmm, I take that back, currently nothing is dependant on glibc-locales
<alezost>swedebugia: with --no-substitutes you'll end up building things locally. Try --dry-run at first and look how many things would be downloaded