unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Dmitry Alexandrov <dag@gnui.org>
To: hot12shots <hot12shots@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Using --search-paths with multiple profiles
Date: Tue, 04 Aug 2020 20:01:57 +0300	[thread overview]
Message-ID: <3652e456.dag@gnui.org> (raw)
In-Reply-To: <CAAkdc5AbMfBFZTOnC5-XmU+aZhXR+tSKWtS3sSBDMN_pZzkOGA@mail.gmail.com> (hot12shots@gmail.com's message of "Mon, 3 Aug 2020 23:26:59 +0000")

[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]

hot12shots <hot12shots@gmail.com> wrote:
>     guix package --search-paths=prefix \
>                  -p /run/current-system/profile  \
>                  -p ~/.config/guix/current       \
>                  -p ~/.guix-profile              \
>                  -p $GUIX_EXTRA_PROFILES/abc/abc \
>                  -p $GUIX_EXTRA_PROFILES/xyz/zyz
>                  # etc.
>
> This properly sets the manpath etc., as the consuming packages (man-db and friends) are present in the included "built-in" profiles (first 3 `-p` arguments listed above).

Ha!  Nice trick, thanks.  Alas, it wonʼt help much on top of foreign distribution, where they often are not.

> 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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2020-08-04 17:10 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 [this message]
2020-08-05 21:13   ` hot12shots

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=3652e456.dag@gnui.org \
    --to=dag@gnui.org \
    --cc=help-guix@gnu.org \
    --cc=hot12shots@gmail.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.
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).