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