1 |
On 09/16/2014 02:37 PM, Bertrand Simonnet wrote: |
2 |
> |
3 |
> |
4 |
> On Tue, Sep 16, 2014 at 12:17 PM, Zac Medico <zmedico@g.o |
5 |
> <mailto:zmedico@g.o>> wrote: |
6 |
> |
7 |
> On 09/16/2014 11:17 AM, Bertrand Simonnet wrote: |
8 |
> > I moved the profile attributes detection logic into the python side as |
9 |
> > suggested (much cleaner). |
10 |
> |
11 |
> Thanks, that's better. I've got a couple more issues though: |
12 |
> |
13 |
> 1) Like global functions, global variables should also be unset in |
14 |
> __save_ebuild_env. So, we should unset PORTAGE_PROFILE_ATTRIBUTES there. |
15 |
> |
16 |
> Done |
17 |
> |
18 |
> 2) Instead of having _get_profile_attributes read the layout.conf files |
19 |
> directly, it would be nicer if we could integrated it with the |
20 |
> LocationsManager layout.conf parsing. For example, see the |
21 |
> intersecting_repos code inside the _addProfile method. |
22 |
> |
23 |
> This is much better. :) |
24 |
|
25 |
I all looks very well done to me now. I'd encourage others on the list |
26 |
to review it now, in case there's anything that I missed. |
27 |
-- |
28 |
Thanks, |
29 |
Zac |