missed to install it, then the "git verify-commit" prints some error messages
with "error: cannot run gpg". And unfortunately gpg is not the package name to
install to solve this error.
It would be beneficial, if the two required packages git (or git-minimal?) and
gnupg woul
Andreas Enge skribis:
> Am Donnerstag, 7. Februar 2013 schrieb Ludovic Courtès:
>> Andreas Enge skribis:
>> > In my attempt to install guix from guix, I came upon the problem that
>> > the libgcrypt headers require the libgpg-error headers. This is a
>> > propagated input, so should in the futur
Am Donnerstag, 7. Februar 2013 schrieb Ludovic Courtès:
> Andreas Enge skribis:
> > In my attempt to install guix from guix, I came upon the problem that
> > the libgcrypt headers require the libgpg-error headers. This is a
> > propagated input, so should in the future be installed automatically.
Andreas Enge skribis:
> Am Mittwoch, 6. Februar 2013 schrieb Ludovic Courtès:
>> > OK. That’s “user-environment-propagated-inputs”. We could achieve
>> > that by just changing guix-profile to install propagated inputs.
>> > That’s probably the right thing to do anyway.
>> Commit 4dede02 implem
Andreas Enge skribis:
> Now I get the following error:
> Backtrace:
> In ice-9/boot-9.scm:
> 157: 5 [catch #t # ...]
> In unknown file:
>?: 4 [apply-smob/1 #]
> In ice-9/boot-9.scm:
> 63: 3 [call-with-prompt prompt0 ...]
> In ice-9/eval.scm:
> 421: 2 [eval # #]
> In /home/privat/.guix-pro
Andreas Enge skribis:
> In my attempt to install guix from guix, I came upon the problem that the
> libgcrypt headers require the libgpg-error headers. This is a propagated
> input, so should in the future be installed automatically.
The future is actually yesterday. :-)
> However, the next
Am Mittwoch, 6. Februar 2013 schrieb Ludovic Courtès:
> > OK. That’s “user-environment-propagated-inputs”. We could achieve
> > that by just changing guix-profile to install propagated inputs.
> > That’s probably the right thing to do anyway.
> Commit 4dede02 implements that.
It apparently work
Concerning more checking in configure.ac:
The files included from nix require sqlite, it would be good to add a check
for that.
Now I get the following error:
Backtrace:
In ice-9/boot-9.scm:
157: 5 [catch #t # ...]
In unknown file:
?: 4 [apply-smob/1 #]
In ice-9/boot-9.scm:
63: 3 [call-with
Am Mittwoch, 6. Februar 2013 schrieb Ludovic Courtès:
\> > OK. That’s “user-environment-propagated-inputs”. We could achieve
> > that by just changing guix-profile to install propagated inputs.
> > That’s probably the right thing to do anyway.
>
> Commit 4dede02 implements that.
Good initiativ
Hi!
l...@gnu.org (Ludovic Courtès) skribis:
> Andreas Enge skribis:
>
>> Am Montag, 4. Februar 2013 schrieb Ludovic Courtès:
>>> Andreas Enge skribis:
>>> > A question related to my previous posting, but also of independent
>>> > justification: Should we maybe implement somthing similar to the
Am Dienstag, 5. Februar 2013 schrieb Ludovic Courtès:
> For GCC, the situation is more complicated, because GCC has a loose tie
> to Binutils and libc. For instance, it happily takes whichever ‘ld’
> program is in $PATH. It’s more closely tied to libc, though, because we
> explicitly patch its sp
Andreas Enge skribis:
> Am Montag, 4. Februar 2013 schrieb Ludovic Courtès:
>> Andreas Enge skribis:
>> > A question related to my previous posting, but also of independent
>> > justification: Should we maybe implement somthing similar to the
>> > "depends" field of Debian packages?
>> What’s th
Am Montag, 4. Februar 2013 schrieb Ludovic Courtès:
> Andreas Enge skribis:
> > A question related to my previous posting, but also of independent
> > justification: Should we maybe implement somthing similar to the
> > "depends" field of Debian packages?
> What’s this?
When A "depends on" B in d
Andreas Enge skribis:
> A question related to my previous posting, but also of independent
> justification: Should we maybe implement somthing similar to the "depends"
> field of Debian packages?
What’s this?
> For instance, programming with mpc also requires mpfr and gmp; in fact, the
> fir
A question related to my previous posting, but also of independent
justification: Should we maybe implement somthing similar to the "depends"
field of Debian packages?
For instance, programming with mpc also requires mpfr and gmp; in fact, the
first few lines of mpc.h read
#include "gmp.h"
15 matches
Mail list logo
