From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Guix Devel <guix-devel@gnu.org>, James Thomas <jimjoe@gmx.net>,
Jim <jimplyl@outlook.com>
Subject: Re: Using Guix inside a Guix container
Date: Wed, 15 Feb 2023 10:49:48 +0100 [thread overview]
Message-ID: <m13577cl6r.fsf@fastmail.net> (raw)
In-Reply-To: <87r0utize9.fsf@gmx.net>
James Thomas <jimjoe@gmx.net> writes:
> Makes sense to me, because the guix package definition was only updated
> with the new release (see 'guix edit guix'). Maybe you can try:
Indeed. That's at least an explanation, though I still don't see *why*
it is done this way. In fact, the role of the package "guix" isn't
really clear to me.\
> guix shell -C guix --with-version=guix=VERSION -- guix describe
>
> Or --with-commit etc.
That's an interesting idea! I could also define my own package (in a
file) called "guix-current" or something like that, which inherits from
"guix" and updates the commit.
Jim <jimplyl@outlook.com> writes:
> Or even:
>
> guix shell -C -p /var/guix/profiles/per-user/.../current-guix -- guix
> describe
That would create a container from the Guix profile. Not sure if this
works at all, but it's very probably not what I want because I have to
add other packages to my container, to get some real work done :-)
Thanks to both of you for your suggestions!
Cheers,
Konrad
next prev parent reply other threads:[~2023-02-15 10:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 16:52 Using Guix inside a Guix container Konrad Hinsen
2023-02-03 17:35 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-02-13 11:21 ` James Thomas
2023-02-13 12:35 ` Jim
2023-02-15 9:49 ` Konrad Hinsen [this message]
2023-02-17 15:41 ` Simon Tournier
2023-02-18 9:21 ` Konrad Hinsen
2023-03-13 12:52 ` Simon Tournier
2023-02-21 22:50 ` Ludovic Courtès
2023-02-27 14:27 ` 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=m13577cl6r.fsf@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=guix-devel@gnu.org \
--cc=jimjoe@gmx.net \
--cc=jimplyl@outlook.com \
/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).