From: "Ludovic Courtès" <ludo@gnu.org>
To: sirgazil <sirgazil@zoho.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Adding a subcommand "load-profile"
Date: Sun, 03 May 2020 22:31:21 +0200 [thread overview]
Message-ID: <87ftcgwyjq.fsf@gnu.org> (raw)
In-Reply-To: <171c1dae752.b806970b21211.4448157853317564236@zoho.com> (sirgazil@zoho.com's message of "Tue, 28 Apr 2020 17:34:40 +0000")
Hi,
sirgazil <sirgazil@zoho.com> skribis:
> ---- On Tue, 28 Apr 2020 22:42:53 +0000 Roel Janssen <roel@gnu.org> wrote ----
[...]
> > We added a subcommand in the "guixr" script called "load-profile". It allows a
> > user to do the following:
> > --------------------------------------------------------------------------------
> > $ guixr package -i ... -p /my/profile
> > $ guixr load-profile /my/profile
> > [env]$
> > # ... A new shell is spawned here.
> > # Inside this shell only the environment variables in
> > # /my/profile/etc/profile are set ...
> > [env]$ exit
> > # Return to the normal shell state
> > --------------------------------------------------------------------------------
[...]
> Personally, I think managing Guix profiles is currently difficult, and I would like to have commands like this one to make it easier.
I’m interested in your feedback then.
To me, there are already several ways to do that, notably:
1. guix environment (but it’s slower)
2. sh
. /my/profile/etc/profile.sh
exit
3. sh
eval `guix package -p /my/profile --search-paths`
exit
Options #2 and #3 are more verbose, and less obvious to someone not
familiar with the shell.
Still, such commands are targeting shell users, which makes me wonder
how far we should go. It’s an honest question: I’m torn between the
will to provide a simple CLI, and the need to avoid proliferation of
commands all more or less equivalent.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2020-05-03 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 15:42 Adding a subcommand "load-profile" Roel Janssen
2020-04-28 16:54 ` zimoun
2020-04-29 12:47 ` Roel Janssen
2020-04-29 13:48 ` zimoun
2020-04-29 19:14 ` Roel Janssen
2020-04-28 17:34 ` sirgazil
2020-05-03 20:31 ` Ludovic Courtès [this message]
2020-05-03 20:56 ` Vagrant Cascadian
2020-05-04 13:36 ` zimoun
2020-05-05 8:52 ` Ludovic Courtès
2020-05-04 13:34 ` zimoun
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=87ftcgwyjq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=sirgazil@zoho.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).