| 1 |
On 03/02/2013 04:07 PM, Michał Górny wrote: |
| 2 |
> I don't think you should introduce workarounds in your eclass. I think |
| 3 |
> multilib-build should be the place to do that. |
| 4 |
|
| 5 |
Feel free to implement a solution. I think an explicit variable might |
| 6 |
even be better instead of some magical checks which could cause |
| 7 |
unexpected behavior for in-source builds or ebuilds that do a lot of |
| 8 |
additional stuff on top of these eclasses. |
| 9 |
So in case that solution breaks something, it would only be for |
| 10 |
multilib-portage and they could still handle that via masking those |
| 11 |
packages. |
| 12 |
|
| 13 |
> |
| 14 |
> And please don't attach patches to patched version since that's too |
| 15 |
> hard to follow. |
| 16 |
> |
| 17 |
|
| 18 |
I didn't. However, here is the full version. |
Archives