Am 13.12.20 um 14:21 schrieb Christopher Baines:
I think if you add openssl to --ad-hoc along with nss-certs, then you
should get the search paths setup.
Thanks, this did the trick
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goe...@crazy-compilers.com |
| www.crazy-c
Hartmut Goebel writes:
> Hi,
>
> for setting up a guix development environment, the manual recommends
>
>guix environment guix
>
> Anyhow, this is not enough, since e.g "./preinst-env guix lint" will
> fail with "TLS certificate error". Also
>
>guix environment guix --ad-hoc nss-certs
>
Hi,
for setting up a guix development environment, the manual recommends
guix environment guix
Anyhow, this is not enough, since e.g "./preinst-env guix lint" will
fail with "TLS certificate error". Also
guix environment guix --ad-hoc nss-certs
does not succeed, since SSL_CERT_DIR sti
On Fri, Jan 13, 2017 at 02:14:24PM +0100, Ludovic Courtès wrote:
> Hello!
Hej Ludó!
> The problem is that you never know whether a package is reproducible.
I see the philosophical debate you had at the summit, but
I think most users would be fine with something pragmatic
that *improves* the prob
Hello!
carlo von lynX skribis:
> Congrats! ng0 just showed me
> https://www.gnu.org/software/guix/packages/reproducibility.html
Spoiler alert! :-)
(I haven’t mentioned it on the list yet because it’s not fully baked.)
> Great file.. and great that I only saw some twenty important
> packages
Congrats! ng0 just showed me
https://www.gnu.org/software/guix/packages/reproducibility.html
Great file.. and great that I only saw some twenty important
packages that need to be built manually.. most of the stuff
is trustworthy in binary form. EXCELLENT!
Now the perfect thing would be that this
On Mon, Sep 19, 2016 at 11:06:40AM +, ng0 wrote:
> Leo Famulari writes:
> > Basically, we need someone to be a reproducibility champion in Guix! We
> > have all the tools to test reproducibility, but somebody needs to
> > implement a system to actually perform the tests automatically
>
> Do w
Leo Famulari writes:
> [ Unknown signature status ]
> On Fri, Sep 16, 2016 at 07:11:00PM +0200, carlo von lynX wrote:
>> Hello everyone!
>
> Hi, welcome!
>
>> Some questions I couldn't resolve from manuals and searches:
>
> It's always good to hear this kind of question!
>
>> I haven't figured ou
On Fri, Sep 16, 2016 at 07:11:00PM +0200, carlo von lynX wrote:
> Hello everyone!
Hi, welcome!
> Some questions I couldn't resolve from manuals and searches:
It's always good to hear this kind of question!
> I haven't figured out if there is a way to know which packages
> are reproducible. I wo
Hello everyone!
Some questions I couldn't resolve from manuals and searches:
I haven't figured out if there is a way to know which packages
are reproducible. I would like to configure my guix to only
fetch binaries that a sufficient number of people agree on to
be deterministic - and for a start
On Wed, May 27, 2015 at 10:15:23PM +0200, Ludovic Courtès wrote:
> Andreas Enge skribis:
> >> Currently, fontconfig from Guix do not use '/etc/fonts/fonts.conf',
> >> and hardcode ~/.guix-profile/share/fonts (which think is a bad idea).
> > It has the advantage of working out-of-the-box for Guix o
Andreas Enge skribis:
> On Wed, May 27, 2015 at 10:02:31PM +0800, 宋文武 wrote:
>> Currently, fontconfig from Guix do not use '/etc/fonts/fonts.conf',
>> and hardcode ~/.guix-profile/share/fonts (which think is a bad idea).
>
> It has the advantage of working out-of-the-box for Guix on top of anothe
On Wed, May 27, 2015 at 10:02:31PM +0800, 宋文武 wrote:
> Currently, fontconfig from Guix do not use '/etc/fonts/fonts.conf',
> and hardcode ~/.guix-profile/share/fonts (which think is a bad idea).
It has the advantage of working out-of-the-box for Guix on top of another
distro.
Andreas
Ludovic Courtès writes:
> "Feng Shu" skribis:
>
>> I use guix to build my own version of emacs-snapshot and sawfish, and
>> find some integrate-issue, and suggest add a FAQ to deal with,
>> for example:
>>
>> 1. How to use fonts which is outside gu
Please keep the list Cc’d.
Feng Shu skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Good questions! I drafted a section on how to use Guix on another
>> GNU/Linux distro, and these are the typical things that need to be
>> answered in that section:
>>
>> http://lists.gnu.org/archive/ht
"Feng Shu" skribis:
> I use guix to build my own version of emacs-snapshot and sawfish, and
> find some integrate-issue, and suggest add a FAQ to deal with,
> for example:
>
> 1. How to use fonts which is outside guix?
> 2. How to use fonts config which is outside gui
I use guix to build my own version of emacs-snapshot and sawfish, and
find some integrate-issue, and suggest add a FAQ to deal with,
for example:
1. How to use fonts which is outside guix?
2. How to use fonts config which is outside guix?
3. How to use gtk or qt theme similar with outside guix
Nikita Karetnikov skribis:
>> Sorry if I wasn’t clear. What I meant is: instead of presenting it as a
>> trial-and-error approach, I would rather present it as a sequence of
>> instructions to build from Git.
>
> OK, what do you think about this patch?
Looks good to me!
One last thing:
> +* B
> Sorry if I wasn’t clear. What I meant is: instead of presenting it as a
> trial-and-error approach, I would rather present it as a sequence of
> instructions to build from Git.
OK, what do you think about this patch?
> For the link to README, just use [[./README][README]] (info "(org)
> Hyperl
Nikita Karetnikov skribis:
> +* Building from Git
> +
> +The following errors might appear if you are building from Git. Also,
> +take a look at the
> [[https://gnu.org/software/guix/manual/guix.html#Installation]["Installation";]]
> section of the manual and the
> +[[http://git.savannah.gnu.o
> I’d say no, because that could lead “normal users” to think they need
> Automake & co. to install Guix.
OK, can I push this one?
From cb6750a9869fc162d98eeb38ccb78e0846553f64 Mon Sep 17 00:00:00 2001
From: Nikita Karetnikov
Date: Wed, 10 Jul 2013 06:13:59 +
Subject: [PATCH] doc: Add "Build
Nikita Karetnikov skribis:
>> Looks good, but I would call it “Building from Git”, for instance, with
>> this particular error as a caveat.
>
> OK.
>
>> Remove “just”.
>
> OK.
>
>> I would also link to the “Installation” section of the manual, and to
>> “Installing Guix from Guix” in README.
>
>>
> Looks good, but I would call it “Building from Git”, for instance, with
> this particular error as a caveat.
OK.
> Remove “just”.
OK.
> I would also link to the “Installation” section of the manual, and to
> “Installing Guix from Guix” in README.
> WDYT?
Can I use 'README' instead of 'HACKI
Nikita Karetnikov skribis:
>> It’s a good idea, probably as the first section in ‘HACKING’. Would you
>> like to propose a patch?
>
> Attached. Did I forget to mention anything?
Looks good, but I would call it “Building from Git”, for instance, with
this particular error as a caveat.
> +You m
[PATCH] doc: Add FAQ to 'HACKING'.
---
HACKING | 20
1 file changed, 20 insertions(+)
diff --git a/HACKING b/HACKING
index dd59a68..89ea124 100644
--- a/HACKING
+++ b/HACKING
@@ -3,12 +3,32 @@
#+TITLE: Hacking GNU Guix and Its Incredible Distro
Copyright © 20
Nikita Karetnikov skribis:
>> Yes, but the Automake you installed by hand (in /usr/local I suppose?)
>> doesn’t look for .m4 files under /usr/share. Thus you need to:
>
>> export ACLOCAL PATH=/usr/share/aclocal
>
> I've seen similar questions several time
> Yes, but the Automake you installed by hand (in /usr/local I suppose?)
> doesn’t look for .m4 files under /usr/share. Thus you need to:
> export ACLOCAL PATH=/usr/share/aclocal
I've seen similar questions several times. Maybe we should create a FAQ
section in 'HACKING&#
27 matches
Mail list logo
