| 1 |
On Fri, 3 Jun 2016 14:33:16 -0700 |
| 2 |
Nick Vinson <nvinson234@×××××.com> wrote: |
| 3 |
|
| 4 |
> On Jun 3, 2016 1:15 PM, "Alan McKinnon" <alan.mckinnon@×××××.com> wrote: |
| 5 |
> > |
| 6 |
> > On 03/06/2016 21:34, waltdnes@××××××××.org wrote: |
| 7 |
> >> |
| 8 |
> >> On Fri, Jun 03, 2016 at 10:35:45AM -0400, Ian Stakenvicius wrote |
| 9 |
> >> |
| 10 |
> >>> USE=gui is about building the graphical user interface that an |
| 11 |
> >>> application offers, when it is optional. That's it. What |
| 12 |
> >>> dependencies that means and so on have nothing to do with the flag. |
| 13 |
> >> |
| 14 |
> >> |
| 15 |
> >> That reasoning may have been valid many years ago when qt was the only |
| 16 |
> >> toolkit around. All GUI-optional apps back then either used qt or wrote |
| 17 |
> >> their own primitives directly to X. Fast-forward to 2016. You now have |
| 18 |
> >> X/Wayland/Mir/qt4/qt5/gtk2/gtk3/fltk/whatever. If a package can have a |
| 19 |
> >> GUI from more than one of the above, you *NEED* to select implementation |
| 20 |
> >> type *SOMEWHERE* (make.conf/package.use/profile). Deal with it. |
| 21 |
> >> |
| 22 |
> >>> You get that use flags are not supposed to represent dependencies |
| 23 |
> >>> right, but features of the package?? |
| 24 |
> >> |
| 25 |
> >> |
| 26 |
> >> Gentoo currently assumes that users are reasonably competent, and that |
| 27 |
> >> if they've selected specific graphics libs to be linked to a package, |
| 28 |
> >> that they've done it for a reason; i.e. to enable a GUI. |
| 29 |
> > |
| 30 |
> > |
| 31 |
> > Walter, |
| 32 |
> > |
| 33 |
> > I think you're missing where the devs want to take this and what USE is |
| 34 |
> all about. It's about *features*, not about dependencies. |
| 35 |
> > |
| 36 |
> > USE="gtk" is a dependency. |
| 37 |
> |
| 38 |
> No. It is a feature. However, it is a feature named after the |
| 39 |
> dependencies needed to enable it. If a package has a hard dependency on |
| 40 |
> libgtk, a USE flag would not be added, but a soft dependency on libgtk |
| 41 |
> means that libgtk support is a feature or part of a feature (the feature |
| 42 |
> being you get to choose which toolkit is used). |
| 43 |
> |
| 44 |
> If it was a dependency, then packages such as XFCE and evince would have to |
| 45 |
> use flags. However they don't. |
| 46 |
> |
| 47 |
> So enough with the these are dependency use flags and those are feature use |
| 48 |
> flags. It's not true and it's a poor attempt to try and force this idea |
| 49 |
> through. If this is idea is a good one, such tactics aren't needed. If |
| 50 |
> it's not, the tactics aren't warranted. |
| 51 |
|
| 52 |
Your statement is not true and is a poor attempt to try and block |
| 53 |
the idea you don't like. If it would be a bad one, such tactics |
| 54 |
wouldn't be needed on your side... |
| 55 |
|
| 56 |
-- |
| 57 |
Best regards, |
| 58 |
Michał Górny |
| 59 |
<http://dev.gentoo.org/~mgorny/> |
Archives