From: hot12shots <hot12shots@gmail.com>
To: Dmitry Alexandrov <dag@gnui.org>
Cc: help-guix@gnu.org
Subject: Re: Using --search-paths with multiple profiles
Date: Wed, 5 Aug 2020 21:13:01 +0000 [thread overview]
Message-ID: <CAAkdc5ADeYEthcH8+g6=1s4RDkefw8bM+0_TzEonpChpE40BVQ@mail.gmail.com> (raw)
In-Reply-To: <3652e456.dag@gnui.org>
On Tue, Aug 4, 2020 at 5:01 PM Dmitry Alexandrov <dag@gnui.org> wrote:
> Alas, it wonʼt help much on top of foreign distribution, where they often are not.
True, good point!
On Guix native systems I've discovered another problem as well: the
PATH assignment output by `--search-paths=prefix` can mask
/run/setuid-programs by prepending other path items in front of them,
so PATH has to be fixed manually after applying this change to ensure
sudo etc. don't break.
> > The only caveat I'm aware of is that the multiple `guix` invocations aren't instantaneous, so one might not want to use this if sourcing their .profile from .bashrc or equivalent, as it would add some init time to every shell invocation.
>
> But one should never source profiles from ~/.bashrc in any case! They are supposed to sourced by login shell only. In other words, there is ~/.profile (or ~/.bash_profile) for that.
It's definitely a nonstandard usage, but I think some people do it.
More simply, though, one might want to have .bashrc just activate the
extra Guix profiles, without sourcing .profile. This would be a
workaround to avoid having to restart the login session in order to
get access to newly activated profiles in a shell environment.
prev parent reply other threads:[~2020-08-05 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 23:26 Using --search-paths with multiple profiles hot12shots
2020-08-04 17:01 ` Dmitry Alexandrov
2020-08-05 21:13 ` hot12shots [this message]
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='CAAkdc5ADeYEthcH8+g6=1s4RDkefw8bM+0_TzEonpChpE40BVQ@mail.gmail.com' \
--to=hot12shots@gmail.com \
--cc=dag@gnui.org \
--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).