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