On Wed, Feb 10, 2016 at 02:48:43PM +0100, Nils Gillmann wrote: > Leo Famulari <l...@famulari.name> writes: > > > On Tue, Feb 09, 2016 at 11:30:21AM +0100, Nils Gillmann wrote: > > I'm not sure — did you figure out a solution to the problem with the > > package? > > Yes and no. > I am not sure, as I don't know Guix enough currently. > On Debian, compiled in $HOME I get 644 on SYSATOMS + BASIC.IMG. > If this is the default, should I just assume for a moment that > this will be okay to set for (chmod) in the install procedure and > patch it as such?
I spent some time trying to get this to work without success. Can you elaborate on your workflow? Are you using the `guix environment` tool to create a build environment and then building "by hand" by running `make`, or are you using using `./pre-inst-env guix build`, or some combination of the two? The `./pre-inst-env` method [0] should ensure that if a package works for you, it will work when installed from the master Guix repo. For example, you could build and test a package like this: $ ./pre-inst-env guix build lispf4 && ./pre-inst-env guix package -i lispf4 [0] https://www.gnu.org/software/guix/manual/guix.html#Running-Guix-Before-It-Is-Installed
