| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 11/08/15 09:04 AM, Sergey Popov wrote: |
| 5 |
> 11.08.2015 15:32, Michael Palimaka пишет: |
| 6 |
>> On 11/08/15 20:17, Sergey Popov wrote: |
| 7 |
>>> 09.08.2015 23:28, Ulrich Mueller пишет: |
| 8 |
>>>> I disagree with this. Really, REQUIRED_USE should be used |
| 9 |
>>>> sparingly, and IMHO the above is not a legitimate usage case |
| 10 |
>>>> for it. |
| 11 |
>>> |
| 12 |
>>> So, you prefer to make ugly mess of deps here like i posted |
| 13 |
>>> before or introduce some really unneded USE-flag like 'gui', |
| 14 |
>>> 'qt', etc. to make users even more confused? |
| 15 |
>>> |
| 16 |
>>> Really, look at man-db ebuild. Especially on berkdb and gdbm |
| 17 |
>>> USE flags. And dependency string like this: |
| 18 |
>>> |
| 19 |
>>> !berkdb? ( !gdbm? ( sys-libs/gdbm ) ) |
| 20 |
>>> |
| 21 |
>>> One sentence: "WHAT THE HELL?" |
| 22 |
>>> |
| 23 |
>>> Imagine that it would be dozen of flags. Is it fun to mess with |
| 24 |
>>> deps like this for you? |
| 25 |
>> |
| 26 |
>> Shall we ban this too? |
| 27 |
>> |
| 28 |
>> ffmpeg? ( libav? ( media-video/libav:= ) !libav? ( |
| 29 |
>> media-video/ffmpeg:0= ) ) |
| 30 |
>> |
| 31 |
>> |
| 32 |
>> |
| 33 |
>> |
| 34 |
> |
| 35 |
> No, because ffmpeg here is a feature AND name of concrete |
| 36 |
> realization. Not ideal case as i would said, but it is acceptable. |
| 37 |
> |
| 38 |
> You want to migrate to such decision? Like: |
| 39 |
> |
| 40 |
> qt? ( qt5? ( dev-lang/qtcore:5 ) !qt5? ( dev-lang/qtcore:4 ) ) |
| 41 |
> |
| 42 |
> Fine by me, if you would ask. |
| 43 |
> |
| 44 |
> As i said one message earlier: Something like $(qt_use_default |
| 45 |
> qtgui 5) |
| 46 |
> |
| 47 |
> which will generate something like this: |
| 48 |
> |
| 49 |
> qt4? ( qt5? ( dev-lang/qtcore:5 ) !qt5? ( dev-lang/qtcore:4 ) ) |
| 50 |
> !qt5? ( !qt4? ( dev-lang/qtcore:5 ) ) |
| 51 |
> |
| 52 |
> would help too. |
| 53 |
|
| 54 |
Woah -- why would qt5 be a dep when both flags are off? If you have a |
| 55 |
package that -needs- one version enabled, then in that case I do fully |
| 56 |
support REQUIRED_USE="|| ( qt4 qt5 )". '||' being the one-or-more-of |
| 57 |
operator. |
| 58 |
|
| 59 |
The other alternative here would be that there is no qt5 flag, just a |
| 60 |
qt4 one, and the qt4 one toggles qt5 off and qt4 on. And that just |
| 61 |
isn't pretty, so let's not do that. |
| 62 |
|
| 63 |
And using this form of REQUIRED_USE I believe (if I understand what |
| 64 |
QA's and QT's stances are on this) is not in conflict with either |
| 65 |
group, right? |
| 66 |
|
| 67 |
|
| 68 |
|
| 69 |
-----BEGIN PGP SIGNATURE----- |
| 70 |
Version: GnuPG v2 |
| 71 |
|
| 72 |
iF4EAREIAAYFAlXKDosACgkQAJxUfCtlWe2Z8QD/Z+NvyJ0VXoIQH/KRPy8Asete |
| 73 |
iXZTpA1QgLDh4xYJE9YBAOTV61mJP472jBu/kEmJOK9cZPFW9PfJ15I0IvoBWdNF |
| 74 |
=1oaz |
| 75 |
-----END PGP SIGNATURE----- |
Archives