| 1 |
Hello all, |
| 2 |
|
| 3 |
while working on bug #518422, I found out that while eclass calls the |
| 4 |
relevant cache updates it has no idea whether or not it is called in a |
| 5 |
multilib context or not. |
| 6 |
|
| 7 |
Imho, this leads to avoidable human errors where one thinks eclass will |
| 8 |
take care of lib dependent caches, which it does, but not for all |
| 9 |
enabled ABIs which could lead to reduced functionality for non-native |
| 10 |
ABIs. |
| 11 |
|
| 12 |
While it seems reasonable to call multilib_foreach_abi |
| 13 |
gnome2_pkg_postinst for multilib enabled ebuilds, it is still not ideal |
| 14 |
as it will call a lot of functions for no good reason. On the other |
| 15 |
hand, checking environment variable set by multilib eclasses does not |
| 16 |
seem like a robust solution. |
| 17 |
|
| 18 |
Is there any reasonable way to make phase functions aware of if they |
| 19 |
are running in a multilib enabled ebuild to adjust their behavior ? |
| 20 |
|
| 21 |
-- |
| 22 |
Gilles Dartiguelongue <eva@g.o> |
| 23 |
Gentoo |
Archives