[gentoo-portage-dev] [PATCH] per package environment: generalize the mechanism to be profile specific

[Bertrand Simonnet]

Hi guys,

I have been working on a patch to make package.env (and env/ files)
stackable with the profiles.
The main goal would be to have a mechanism to be able to define a
per-package, per-profile environment in a simple way.

We can currently do this with profile.bashrc but we have to add some logic
there to decide which package are relevant which already exist in ebuild.sh
and pym/*.

I attached my current patch which contain two main modifications:
- ebuild.sh walk the profile and source all scripts with path:
${profile_path}/env/${category}/${PN}
- config.py imports package.env from all profiles and then from
/etc/portage/package.env

Note:
* I gated the env/$CATEGORY/$PN scripts with a new feature: per-profile-env.
   I couldn't do this with package.env as the scripts are parsed before we
initialize self.features.
* I am not particularly attach to both package.env and env/$CATEGORY/$PN.
It might make more sense to have only env/$CATEGORY/$PN, especially
considering the problem with package.env.

Do you have any suggestions on this patch ?

Would you be willing to accept this patch once the few problems are sorted
out ?

Thanks!