all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: myglc2@gmail.com, 31841@debbugs.gnu.org,
	Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: bug#31841: ./pre-inst-env guix system no longer works without ~/.config/guix
Date: Sat, 16 Jun 2018 05:50:00 -0400	[thread overview]
Message-ID: <87po0r3vsn.fsf@netris.org> (raw)
In-Reply-To: <87sh5nqgtf.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 16 Jun 2018 10:25:00 +0200")

Hi,

ludo@gnu.org (Ludovic Courtès) writes:

> myglc2@gmail.com skribis:
>
>> Based on this thread I am now making guix like this ...
>>
>> guix environment guix --ad-hoc guile-sqlite3 --root=build-env -- make [MAKECMDGOALS]
>>
>> ... and using it like this ...
>>
>> source build-env/etc/profile
>> ./pre-inst-env guix COMMAND ARGS...
>
> Yeah we can improve the doc.  Currently, “Building from Git” mentions
> ‘guix environment guix’, but “Running Guix Before It Is Installed”
> doesn’t.  How about this:
>
> diff --git a/doc/contributing.texi b/doc/contributing.texi
> index 205c972ae..3f82f4bc2 100644
> --- a/doc/contributing.texi
> +++ b/doc/contributing.texi
> @@ -108,7 +108,9 @@ actually installing them.  So that you can distinguish between your
>  ``end-user'' hat and your ``motley'' costume.
>  
>  To that end, all the command-line tools can be used even if you have not
> -run @code{make install}.  To do that, prefix each command with
> +run @code{make install}.  To do that, you first need to have an environment
> +with all the dependencies available (@pxref{Building from Git}), and then
> +simply prefix each command with
>  @command{./pre-inst-env} (the @file{pre-inst-env} script lives in the
>  top build tree of Guix), as in@footnote{The @option{-E} flag to
>  @command{sudo} guarantees that @code{GUILE_LOAD_PATH} is correctly set
>
>
> Note that I purposely did not mention “--ad-hoc guile-sqlite3” because
> it has become unnecessary with commit
> c5a2e1ffcb029f50c4c18352cf378b61c41c625e.
>
> Likewise, I did not mention “source build-env/etc/profile” because
> “Building from Git” suggests using ‘guix environment guix’, which sets
> up the right environment variables.
>
> WDYT?

When running Guix exclusively from a git checkout and never running
'guix pull', something like "source build-env/etc/profile" must now be
run before running 'guix'.

You seem to be suggesting that "source build-env/etc/profile" could
simply be replaced by "guix environment guix".  One problem with this
idea is that it would introduce a circularity.  My 'guix' script cannot
very well begin by running 'guix environment guix'.

There are other problems as well:

(1) The build environment used to build the git checkout must be
    registered as a GC root, or else "guix gc" may render my git
    checkout of 'guix' non-functional, with no easy way to recover
    (at least not without running 'guix pull').

(2) When my git checkout is in a bad state, or is unbuilt, then during
    this time I'm unable to easily run "guix environment guix".  So, I
    always need a way to restore a known good development environment to
    rebuild my copy of guix, without using guix itself.  My method is to
    source the etc/profile from my saved development environment profile.

I should emphasize that when running Guix this way, if you wish to avoid
running 'guix pull', it's important to always keep at least one
known-good development environment for Guix saved as a GC root.  Toward
that end, when I run "guix environment guix" to update my development
environment profile, I make sure to preserve my previous profile as a GC
root until I'm confident that my new profile is working.

The suggested recipe involving "guix environment guix --root=build-env"
command is a nice improvement over my manual management of these GC
roots, but it has one shortcoming: it discards the older profile symlink
and GC root immediately, before it's known whether the new profile works.

This message should make it clear that when using Guix in this way, it's
easy to get stuck if you're not careful.  I suppose that I could always
get unstuck by running 'guix pull', but I prefer to avoid it.

     Regards,
       Mark

  reply	other threads:[~2018-06-16  9:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15  2:24 bug#31841: ./pre-inst-env guix system no longer works without ~/.config/guix Mark H Weaver
2018-06-15  6:56 ` Rutger Helling
2018-06-15 10:56   ` myglc2
2018-06-15 11:24 ` Ricardo Wurmus
2018-06-15 11:45   ` Ludovic Courtès
2018-06-15 12:04     ` Ricardo Wurmus
2018-06-15 13:08       ` Mark H Weaver
2018-06-15 13:40     ` Mark H Weaver
2018-06-15 16:51       ` Ludovic Courtès
2018-06-15 22:56         ` myglc2
2018-06-16  8:06           ` Mark H Weaver
2018-06-16  8:25           ` Ludovic Courtès
2018-06-16  9:50             ` Mark H Weaver [this message]
2018-06-16 14:31               ` George Clemmer
2018-06-17 20:53               ` Ludovic Courtès
2018-06-19 17:08                 ` myglc2
2018-06-20 14:06                   ` Ludovic Courtès
2018-06-16  7:51         ` Mark H Weaver
2018-06-17 12:54 ` bug#31841: Status: Guix requires guile-sqlite3 Maxim Cournoyer
2018-06-17 21:19   ` Ludovic Courtès
2018-06-18  1:34     ` Maxim Cournoyer

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=87po0r3vsn.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=31841@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=myglc2@gmail.com \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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.