unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: help-guix@gnu.org
Subject: Re: Permanently available environments
Date: Fri, 28 Jan 2022 19:04:07 +0100	[thread overview]
Message-ID: <m1pmobhh48.fsf@fastmail.net> (raw)
In-Reply-To: <m1wnikgluu.fsf@fastmail.net>

Konrad Hinsen <konrad.hinsen@fastmail.net> writes:

> 1. Containers can only be generated using "guix shell" or the older
>    "guix environment". There is no way to generate a container based
>    on a profile. Correct me if I am wrong!

Thanks to Ricardo and Guillaume, who pointed out the –profile option to
"guix shell", which does exactly what I need. I missed it because it is
not mentioned in the manual. I just submitted a patch.

> 4. In practice, I often work with a bad or non-existing network
>    connection, so I must be sure to have all my packages in the store.
>    And if I use "time-machine", I must also keep the required Guix
>    version locally available. But there is no option for that in
>    "time-machine". The Guix versions it downloads are garbage-collected
>    after a while. So I can find myself in the situation of having all
>    the packages for my environment in the store, but unable to access
>    it without a network connection, because "time-machine" first needs
>    to fetch an old Guix version again.

Thanks to Vagrant for pointing out that "guix pull" has a –profile
option as well (which I wasn't aware of). This can indeed serve as a
workaround, although it looks a bit clumsy.

Cheers,
  Konrad.


  parent reply	other threads:[~2022-01-28 18:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 11:07 Permanently available environments Konrad Hinsen
2022-01-28 11:54 ` Ricardo Wurmus
2022-01-28 12:24 ` Guillaume Le Vaillant
2022-01-28 17:19 ` Vagrant Cascadian
2022-01-28 18:04 ` Konrad Hinsen [this message]
2022-03-08 10:19   ` Ludovic Courtès
2022-03-10 14:11     ` Konrad Hinsen

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=m1pmobhh48.fsf@fastmail.net \
    --to=konrad.hinsen@fastmail.net \
    --cc=help-guix@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.
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).