| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 11/08/15 10:19 AM, Rich Freeman wrote: |
| 5 |
> On Tue, Aug 11, 2015 at 9:42 AM, Sergey Popov <pinkbyte@g.o> |
| 6 |
> wrote: |
| 7 |
>> 11.08.2015 16:36, Rich Freeman пишет: |
| 8 |
>>> On Tue, Aug 11, 2015 at 9:19 AM, Sergey Popov |
| 9 |
>>> <pinkbyte@g.o> wrote: |
| 10 |
>>>> 11.08.2015 16:11, James Le Cuirot пишет: |
| 11 |
>>>>> On Tue, 11 Aug 2015 15:58:49 +0300 Sergey Popov |
| 12 |
>>>>> <pinkbyte@g.o> wrote: |
| 13 |
>>>>> |
| 14 |
>>>>>> If both of flags are not set - we stick to default. |
| 15 |
>>>>>> Should this be set in EVERY ebuild explicitly? |
| 16 |
>>>>>> |
| 17 |
>>>>>> Maybe provide some sugar like $(qt_use_default qtgui 5), |
| 18 |
>>>>>> where qt_use_default is the name of function, qtgui is |
| 19 |
>>>>>> the package and 5 is the slot for default choice, where |
| 20 |
>>>>>> either BOTH of flags(qt4, qt5) are enabled or disabled |
| 21 |
>>>>> |
| 22 |
>>>>> That sounds a little bit like what I suggested earlier. |
| 23 |
>>>>> |
| 24 |
>>>>> https://archives.gentoo.org/gentoo-dev/message/884257a2d924a51851d |
| 25 |
629b1dc9b30df |
| 26 |
>>>>> |
| 27 |
>>>> |
| 28 |
>>>> |
| 29 |
>>>>> |
| 30 |
But without introducing brand new useless USE flag. Which makes huge |
| 31 |
>>>> difference to me :-) |
| 32 |
>>>> |
| 33 |
>>> |
| 34 |
>>> If we want the typical user to not set either qt4 or qt5, are |
| 35 |
>>> we saying that any package that could use either always enable |
| 36 |
>>> one of them by default? Then all users get a GUI by default, |
| 37 |
>>> and then users have to explicitly disable it? That seems to be |
| 38 |
>>> the opposite of how we normally do things, but it does let you |
| 39 |
>>> get away from having lots of users turning on qt. |
| 40 |
>> |
| 41 |
>> I suggested this for packages, where GUI can not be disabled AND |
| 42 |
>> it should be either qt4 or qt5. Then, if we do not add + to USE |
| 43 |
>> description, users without anything in make.conf just run the |
| 44 |
>> blocker |
| 45 |
>> |
| 46 |
> |
| 47 |
> What if the GUI can be disabled? Should we force users to set |
| 48 |
> USE="-qt4 -qt5" to disable the GUI? Or should we force users to |
| 49 |
> put one of those in their make.conf or profile to enable it |
| 50 |
> (causing problems with packages that don't allow both)? |
| 51 |
> |
| 52 |
|
| 53 |
I think the idea with USE="gui" is that the generic profiles then no |
| 54 |
longer need any qt4/qt5/gtk3/whatever flags in them at all, and the |
| 55 |
ebuilds themselves can set a single default-enable on the particular |
| 56 |
flag that should be used by default, thus allowing REQUIRED_USE to be |
| 57 |
satisfied by default when an end-user doesn't care. |
| 58 |
|
| 59 |
However, I agree that USE=gui still has the problem where the |
| 60 |
sub-flags have active state in VDB, meaning that any change to the |
| 61 |
sub-flags will trigger rebuilds on -N even if USE="-gui". And since |
| 62 |
(if i understand this thread correctly) part of the reason for doing |
| 63 |
all of this is to ensure VDB is as "accurate" as possible to what the |
| 64 |
package actually uses/needs/depends on/etc, we end up not having |
| 65 |
solved anything. |
| 66 |
|
| 67 |
|
| 68 |
-----BEGIN PGP SIGNATURE----- |
| 69 |
Version: GnuPG v2 |
| 70 |
|
| 71 |
iF4EAREIAAYFAlXKEmUACgkQAJxUfCtlWe3fowEA6Sx5CtDme6K2h5Yu0yYrfUnb |
| 72 |
2ZunvwQFlv4QAD+fQ1wA/3aX/kfviD+FttzxHgWBH3uGg1SX8DHNCFptfv9y2lJe |
| 73 |
=6i3x |
| 74 |
-----END PGP SIGNATURE----- |
Archives