all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nils Gillmann <ng0@n0.is>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Building guix-modular with cuirass
Date: Tue, 8 May 2018 21:23:56 +0000	[thread overview]
Message-ID: <20180508212356.obhxtfvhc6ysjkjr@abyayala> (raw)
In-Reply-To: <878t93nlha.fsf@gnu.org>

Ludovic Courtès transcribed 800 bytes:
> Hello,
> 
> Mathieu Othacehe <m.othacehe@gmail.com> skribis:
> 
> >> If you add a similar entry on your server, it should be fine.
> >>
> >> Can you try and report back?
> >
> > Yes you're right it works fine, thanks :)
> >
> > However, some of my machines are not picking up the substitutes builded
> > while running 'guix pull'.
> >
> > I found why, on machines that I didn't reconfigure recently,
> > 'default-guile' is guile-2.2.2, while on the cuirass machine it is
> > guile-2.2.3. When reconfiguring them before, substitutes are picked-up
> > correctly.
> 
> Oh indeed.
> 
> In the near future, I want ‘guix pull’ to install a ‘guix’ binary as
> opposed to simply dropping a bunch of modules in ~/.config/guix/latest.
> At that point we won’t have this kind of problem anymore.
> 
> Ludo’.
> 

Not trying to derail this thread too much, but could you explain that a
bit more Ludovic? I'm curious.
This is moving beyond the current change with modular guix (which still
drops a bunch of modules into the store and compiles them), correct?

  parent reply	other threads:[~2018-05-08 21:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27  9:10 Building guix-modular with cuirass Mathieu Othacehe
2018-04-30 13:04 ` Ludovic Courtès
2018-04-30 18:29   ` Mathieu Othacehe
2018-05-01 20:56     ` Ludovic Courtès
2018-05-02 13:52       ` Mathieu Othacehe
2018-05-09 22:05         ` Ludovic Courtès
2018-05-08 21:23       ` Nils Gillmann [this message]
2018-05-13  2:17         ` Chris Marusich
2018-05-13  7:48           ` swedebugia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180508212356.obhxtfvhc6ysjkjr@abyayala \
    --to=ng0@n0.is \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.