unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org, help-guix@gnu.org
Subject: Re: “Guix Profiles in Practice”
Date: Wed, 06 Nov 2019 09:18:26 +1100	[thread overview]
Message-ID: <87tv7idl1p.fsf@zancanaro.id.au> (raw)
In-Reply-To: <87d0e8lzoh.fsf@ambrevar.xyz>

Hey Pierre,

On Mon, Nov 04 2019, Pierre Neidhardt wrote:
> As I understand it, the current discussion is about "pinning"
> profiles.
> Should any dependency get garbage collected, an environment will 
> need
> Internet access to refetch the missing parts; I think this is 
> what we
> are trying to avoid, regardless of how fast `guix environment` 
> is.
>
> What about `guix environment --pin` instead of `guix develop`?

Have you used `guix environment --root`?

In my git checkout of the Guix repository I once ran `guix 
environment guix --root=.environment`, and now whenever I want to 
hack on Guix I start a shell and `source 
.environment/etc/profile`. The .environment symlink is treated as 
a GC root by Guix, and because I'm not actually invoking Guix 
there's never a risk that it will attempt to fetch anything from 
the internet.

Upgrading the environment is quite easy, and must be done 
manually: I delete the existing symlink and run `guix environment 
guix --root=.environment` again. If I'm feeling paranoid I'll run 
`guix environment guix` once first to make sure it succeeds, 
before deleting the old symlink and adding the 
`--root=.environment` to the end.

Carlo

  reply	other threads:[~2019-11-05 22:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 10:24 “Guix Profiles in Practice” Ludovic Courtès
2019-10-25 16:36 ` Thompson, David
2019-10-25 20:44   ` Pjotr Prins
2019-10-26 10:02     ` Pierre Neidhardt
2019-10-27  8:56       ` Pjotr Prins
2019-10-27 11:30         ` Pierre Neidhardt
2019-10-27 11:43           ` Hartmut Goebel
2019-10-27 20:06           ` Konrad Hinsen
2019-10-27 21:05             ` Pierre Neidhardt
2019-10-28 16:20               ` Konrad Hinsen
2019-10-30  8:36     ` Pierre Neidhardt
2019-10-26  0:34   ` Jonathan Frederickson
2019-10-26  1:19     ` Jonathan Frederickson
2019-10-26 10:00   ` Pierre Neidhardt
2019-10-27  3:29     ` Bengt Richter
2019-10-27  8:49       ` Pierre Neidhardt
2019-10-27 13:33     ` Konrad Hinsen
2019-10-27 13:53       ` Jelle Licht
2019-11-03 14:24   ` Ludovic Courtès
2019-11-03 16:49     ` Jonathan Frederickson
2019-11-04 10:12       ` Pierre Neidhardt
2019-11-04 14:33       ` Ludovic Courtès
2019-11-04 10:10     ` Pierre Neidhardt
2019-11-05 22:18       ` Carlo Zancanaro [this message]
2019-11-06  8:32         ` Pierre Neidhardt
2019-11-06 17:37           ` Ludovic Courtès
2019-11-07 12:42             ` Pierre Neidhardt
2019-10-26 18:32 ` Alex Griffin
2019-10-26 19:38   ` Pierre Neidhardt
  -- strict thread matches above, loose matches on Subject: below --
2019-11-02 18:51 Tanguy Le Carrour
2019-11-02 19:21 ` Pierre Neidhardt

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87tv7idl1p.fsf@zancanaro.id.au \
    --to=carlo@zancanaro.id.au \
    --cc=guix-devel@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).