1 |
On 10/25/2011 02:06 AM, Zac Medico wrote: |
2 |
> On 10/01/2011 10:34 AM, Zac Medico wrote: |
3 |
>> Hi, |
4 |
>> |
5 |
>> As I integrate prefix support into mainline portage, I think it will |
6 |
>> make more sense to use $EROOT instead of $ROOT for keys to portage.db |
7 |
>> and similar map objects. This will also affect the portageq commands |
8 |
>> which take a <root> parameter. The reason that I think $EROOT makes more |
9 |
>> sense for these keys is that it will allow for multiple prefixes to |
10 |
>> exist simultaneously in maps like portage.db. |
11 |
>> |
12 |
>> This won't affect non-prefix users, since $EROOT == $ROOT when $EPREFIX |
13 |
>> is empty. So, I'm asking here because if might affect prefix users who |
14 |
>> use portageq, or any programs installed in a prefix that use the |
15 |
>> sys-apps/portage python API. If necessary, I suppose that python |
16 |
>> programs could have some compatibility code which checks whether or no |
17 |
>> $EROOT is contained in portage.db, and fall back to "/" otherwise. |
18 |
> |
19 |
> Here's the commit to watch out for if/when it gets merged into the |
20 |
> prefix branch: |
21 |
> |
22 |
> http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=a715b65f7bd36409c1283e6911265d1f4405ab7a |
23 |
|
24 |
This change has hit in prefix portage-2.2.01.19833. The only problem |
25 |
that I've noticed so far is that `eselect news` doesn't find news items. |
26 |
I've attached a patch for eselect in order to fix this. The following |
27 |
commit will also have to be applied to prefix portage-2.2.01.19833 in |
28 |
order to make this work correctly: |
29 |
|
30 |
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=174ffd8336ec9914f85f871b7ce78506574d3d9b |
31 |
-- |
32 |
Thanks, |
33 |
Zac |