| 1 |
On 23/01/16 09:21, Michael Palimaka wrote: |
| 2 |
> On 01/23/2016 06:04 AM, Nikos Chantziaras wrote: |
| 3 |
>> I have a weird problem. I have an ebuild where either qt4 or qt5 can be |
| 4 |
>> enabled. They are both disabled by default and I have to choose which |
| 5 |
>> one I want. The ebuild does that with: |
| 6 |
>> |
| 7 |
>> IUSE="qt4 qt5" |
| 8 |
>> REQUIRED_USE="^^ ( qt4 qt5 )" |
| 9 |
>> |
| 10 |
>> I'm on the plasma profile which enabled qt5 automatically. However, |
| 11 |
>> portage complains: |
| 12 |
>> |
| 13 |
>> The following REQUIRED_USE flag constraints are unsatisfied: |
| 14 |
>> exactly-one-of ( qt4 qt5 ) |
| 15 |
>> |
| 16 |
>> The qt4 USE flag is enabled. I can't see where. I didn't enable it |
| 17 |
>> anywhere in any of my /etc/portage/* files. If I emerge with: |
| 18 |
>> |
| 19 |
>> USE="-qt4" emerge package |
| 20 |
>> |
| 21 |
>> then it works. So I have to explicitly disable the qt4 USE flag even |
| 22 |
>> though I didn't enable it in the first place. |
| 23 |
>> |
| 24 |
>> Can someone enlighten me? |
| 25 |
>> |
| 26 |
> |
| 27 |
> Which package is it? We can add an entry to the Plasma profile's |
| 28 |
> package.use to avoid the REQUIRED_USE. |
| 29 |
|
| 30 |
It's my own ebuilds (in an overlay.) I wasn't setting either USE flag in |
| 31 |
the ebuilds at all and this spooked me. Turns out it's the parent |
| 32 |
profile of the plasma profile doing this. |
| 33 |
|
| 34 |
What would be really nice to have in portage is if the profiles were |
| 35 |
able to say "if qt4 and qt5 are both supported but mutually exclusive, |
| 36 |
prefer qt5 unless the user or the ebuild itself has specified |
| 37 |
otherwise". But I guess it would be hairy to implement that. (It would |
| 38 |
help with other such USE flags as well, not just qt4 vs qt5.) |
Archives