1 |
On Wed, 1 Jun 2016 22:13:24 -0400 |
2 |
waltdnes@××××××××.org wrote: |
3 |
|
4 |
> On Wed, Jun 01, 2016 at 07:56:41PM +0200, Micha?? Górny wrote |
5 |
> |
6 |
> > waltdnes@××××××××.org wrote: |
7 |
> > |
8 |
> > > I see this as at least a redundancy, if not a problem. First, let's |
9 |
> > > look at the general case. An optional "UI" (User Interface) is also |
10 |
> > > selected... |
11 |
> > > * via the "tools" useflag 78 times in use.local.desc |
12 |
> > > * via the "ncurses" useflag 10 times in use.local.desc. |
13 |
> > > * for a lot of ebuilds via the "ncurses" useflag in use.desc (So why |
14 |
> > > does "ncurses" show up in use.local.desc ???) |
15 |
> > > |
16 |
> > > There is no need for an additional "TUI" (Text User Interface) use flag |
17 |
> > > for these cases. "tools" and/or "ncurses" tells you enough. Similarly, |
18 |
> > > "GUI" is grab-bag of gtk2/gtk3/qt4/qt5/X/Wayland/whatever. The only |
19 |
> > > thing they have in common is a hard-coded dependancy on graphics libs. |
20 |
> > > "GUI" is an implicit dependancy of gtk2/gtk3/qt4/qt5/X/Wayland/whatever. |
21 |
> > > Using any of them tells you enough. What do we accomplish by requiring |
22 |
> > > one more USE flag? This will also make dependancy resolution of ebuilds |
23 |
> > > more complex, i.e. slower. Why? |
24 |
> > |
25 |
> > Simple regular users don't want to be concerned with choice of toolkit |
26 |
> > for every single package, as long as a GUI is provided. |
27 |
> |
28 |
> Then put one of X/xorg/wayland/mir/qt4/qt5/gtk2/gtk3/fltk into USE in |
29 |
> make.conf. This will *FORCE* a gui where applicable. |
30 |
|
31 |
And also a dozen random things, and USE flag conflicts where multiple |
32 |
GUIs are applicable. |
33 |
|
34 |
> > Furthermore, this matches the recommended USE flag design where the |
35 |
> > more important flags are provided as feature flags, while specific |
36 |
> > dependency choice flags are minor. |
37 |
> |
38 |
> This is going to require *THREE* levels of flags, with the first one |
39 |
> being totally unnecessary... |
40 |
> |
41 |
> Level 1) GUI |
42 |
> |
43 |
> Level 2) X or xorg or Wayland or Mir |
44 |
> |
45 |
> Level 3) qt4 or qt5 or gtk2 or gtk3 or fltk |
46 |
> |
47 |
> Let me re-phrase my question... is there *ANY* set of circumstances |
48 |
> under which any of X/xorg/wayland/mir/qt4/qt5/gtk2/gtk3/fltk USE flag |
49 |
> can be set for a package *WITHOUT* requiring a gui? I can see any of X |
50 |
> or xorg or Wayland or Mir being a requirement for any of |
51 |
> qt4/qt5/gtk2/gtk3/fltk. But any of the Level 2 or Level 3 flags *FORCES* |
52 |
> a GUI of one sort or another. |
53 |
> |
54 |
> I repeat, requiring a "GUI" use flag for GUI apps makes as much sense |
55 |
> as requiring a "TUI" flag for commandline apps. I hope I'm not giving |
56 |
> people ideas the wrong way. No I don't want a "TUI" flag either. |
57 |
|
58 |
That's your opinion, and that is how far it goes as I'm concerned. Next |
59 |
thing you complain, that USE=ssl doesn't mean 'openssl only'. |
60 |
|
61 |
-- |
62 |
Best regards, |
63 |
Michał Górny |
64 |
<http://dev.gentoo.org/~mgorny/> |