From: Ian Zimmerman <itz@very.loosely.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Just when is portage/bashrc sourced?
Date: Mon, 27 Nov 2017 09:17:55 -0800 [thread overview]
Message-ID: <20171127171755.xi35ebwexwogsnrf@matica.foolinux.mooo.com> (raw)
In-Reply-To: <ecbba84a-2468-1ba9-b8b1-86078b51843c@gentoo.org>
On 2017-11-27 07:59, Michael Orlitzky wrote:
> > That came up in the OP, but the question was about doing it for
> > selected ebuilds, which is exactly what this must shorter option
> > does.
>
> You should update the wiki, your way is better.
Ah, now I see why I was so confused. the /etc/portage/env/ directory
serves two purposes, only distantly related:
- houses the environment files, referenced from /etc/portage/package.env
These can apparantly contain only variable settings.
- houses the package specific bashrc files, as $CATEGORY/$PN and so on.
These can contain hook definitions and perhaps even more general shell
code.
Both man portage(5) and the wiki treat the two cases separately, so the
fact that the ultimate data files are in the same directory is lost on
the careless reader (such as me). Michael or Neil, if you do edit the
docs please improve this aspect.
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.
prev parent reply other threads:[~2017-11-27 17:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 1:12 [gentoo-user] Just when is portage/bashrc sourced? Ian Zimmerman
2017-11-24 1:21 ` Michael Orlitzky
2017-11-24 8:32 ` Neil Bothwick
2017-11-24 17:07 ` [gentoo-user] " Ian Zimmerman
2017-11-24 17:12 ` Michael Orlitzky
2017-11-24 22:21 ` Neil Bothwick
2017-11-25 1:56 ` Ian Zimmerman
2017-11-25 8:59 ` Neil Bothwick
2017-11-26 20:24 ` Neil Bothwick
2017-11-27 1:57 ` David Haller
2017-11-27 8:35 ` Neil Bothwick
2017-11-27 12:59 ` Michael Orlitzky
2017-11-27 17:17 ` Ian Zimmerman [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171127171755.xi35ebwexwogsnrf@matica.foolinux.mooo.com \
--to=itz@very.loosely.org \
--cc=gentoo-user@lists.gentoo.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