inputs vs. native-inputs vs. propagated-inputs

Hi, I'm a bit confused about the difference between inputs, native-inputs and propagated-inputs. The manual states: The distinction between ‘native-inputs’ and ‘inputs’ is necessary when considering cross-compilation. When cross-compiling, dependencies listed in ‘i

Stuck with corrupt store

Hi, I'm stuck with a corrupt store and can't repair it. I deleted /gnu/store/*-nose-* (can't remember why). Then I ran guix gc --verify=repair which reports path `/gnu/store/…-python-nose-1.3.7' disappeared, but it still has valid referrers! Okay, so let's remove the referrers, too: guix

Re: inputs vs. native-inputs vs. propagated-inputs

Hartmut Goebel writes: > Hi, > > I'm a bit confused about the difference between inputs, native-inputs > and propagated-inputs. > > The manual states: > > The distinction between ‘native-inputs’ and ‘inputs’ is > necessary when considering cross-compilation. When >

Re: inputs vs. native-inputs vs. propagated-inputs

Hi, Thanks for your answer Am 12.06.2016 um 14:38 schrieb 宋文武: > Hartmut Goebel writes: >> For for I understand. But then the manual says: >> >> ‘native-inputs’ is typically used to list tools needed at >> build time, but not at run time, such as Autoconf, Automake, >>

Re: Stuck with corrupt store

Hi! Hartmut Goebel skribis: > I deleted /gnu/store/*-nose-* (can't remember why). You deleted with “rm -rf”? In that case, even though ‘guix gc --verify=repair’ should be able to help, remember that this voids your warranty. :-) > Further when I run guix gc, I get an "FOREIGN KEY constraint

Re: Stuck with corrupt store

Hi, Am 12.06.2016 um 18:19 schrieb Ludovic Courtès: > Hartmut Goebel skribis: > >> I deleted /gnu/store/*-nose-* (can't remember why). > You deleted with “rm -rf”? > > In that case, even though ‘guix gc --verify=repair’ should be able to > help, remember that this voids your warranty. :-) Well,

Re: inputs vs. native-inputs vs. propagated-inputs

On Sun, Jun 12, 2016 at 05:50:29PM +0200, Hartmut Goebel wrote: > Am 12.06.2016 um 14:38 schrieb 宋文武: > > Hartmut Goebel writes: > >> For for I understand. But then the manual says: > >> > >> ‘native-inputs’ is typically used to list tools needed at > >> build time, but not at

Creating new package for Guix - newbie's question

Hello everybody! I am GuixSD and Guix newcomer. Installation succeeded, but suddenly I found that one of my favorite packages - compton[1], is missing in repos. OK, that is not really a problem - I tried to create this package myself. So, I copied template "hello.scm" from documentation, mod

Re: Creating new package for Guix - newbie's question

Hi Rodion, Welcome to Guix! Here is the fast way; $ mkdir -p ${HOME}/tmp/packages/gnu/packages $ export GUIX_PACKAGE_PATH="${HOME}/tmp/packages" $ mv .scm ${HOME}/tmp/packages/gnu/packages $ guix build If you intend to contribute the package, keep reading. > OK, that is not really a problem

Re: Creating new package for Guix - newbie's question

On Sun, Jun 12, 2016 at 05:24:37PM -0400, Matthew Jordan wrote: > Here is what I do atm for developing packages. That is a very complete list of things to do :) > Build > $ ./bootstrap > $ ./configure --localstate=/var That should be --localstatedir=/var > $ make > $ make check It should be en