| 1 |
On 2017-11-27 07:59, Michael Orlitzky wrote: |
| 2 |
|
| 3 |
> > That came up in the OP, but the question was about doing it for |
| 4 |
> > selected ebuilds, which is exactly what this must shorter option |
| 5 |
> > does. |
| 6 |
> |
| 7 |
> You should update the wiki, your way is better. |
| 8 |
|
| 9 |
Ah, now I see why I was so confused. the /etc/portage/env/ directory |
| 10 |
serves two purposes, only distantly related: |
| 11 |
|
| 12 |
- houses the environment files, referenced from /etc/portage/package.env |
| 13 |
These can apparantly contain only variable settings. |
| 14 |
|
| 15 |
- houses the package specific bashrc files, as $CATEGORY/$PN and so on. |
| 16 |
These can contain hook definitions and perhaps even more general shell |
| 17 |
code. |
| 18 |
|
| 19 |
Both man portage(5) and the wiki treat the two cases separately, so the |
| 20 |
fact that the ultimate data files are in the same directory is lost on |
| 21 |
the careless reader (such as me). Michael or Neil, if you do edit the |
| 22 |
docs please improve this aspect. |
| 23 |
|
| 24 |
-- |
| 25 |
Please don't Cc: me privately on mailing lists and Usenet, |
| 26 |
if you also post the followup to the list or newsgroup. |
| 27 |
To reply privately _only_ on Usenet, fetch the TXT record for the domain. |
Archives