| 1 |
On 09/22/2014 11:43 AM, Bertrand Simonnet wrote: |
| 2 |
> Did you mean env/ files ? |
| 3 |
|
| 4 |
Yes. |
| 5 |
|
| 6 |
> Having a different behaviour for |
| 7 |
> /etc/portage/package.env and $profile/package.env would be confusing. |
| 8 |
|
| 9 |
We could call package.bashenv (or something like that), in order to make |
| 10 |
the difference from package.env clear. |
| 11 |
|
| 12 |
> Parsing env/ atom/files association in python would be a good idea. We |
| 13 |
> should get the benefits of both I believe. |
| 14 |
> The list of files to be sourced by bash could contain all the files |
| 15 |
> relevant to the package in one profile then profile.bashrc, for each |
| 16 |
> profile so that |
| 17 |
> we don't even need to walk all the profiles in ebuild.sh. |
| 18 |
|
| 19 |
Right, that's what I was thinking. |
| 20 |
-- |
| 21 |
Thanks, |
| 22 |
Zac |
Archives