1 |
On Wed, 30 Aug 2017 14:01:08 -0400 |
2 |
"William L. Thomson Jr." <wlt-ml@××××××.com> wrote: |
3 |
|
4 |
> This is more food for thought to start a discussion on new category |
5 |
> names. With Wayland becoming more of a reality every day. I think some |
6 |
> of the x11-* categories may need to change. Stuff in there may not be |
7 |
> bound to X and can run on Wayland or X. |
8 |
> |
9 |
> Examples |
10 |
> x11-libs/gtk+ |
11 |
> x11-terms/terminology |
12 |
> |
13 |
> Not sure what better "universal" category names would be. But seems it |
14 |
> maybe time for a discussion on such and some new categories and |
15 |
> package moves. Given thus stuff can run under X or Wayland. Not sure |
16 |
> x11 makes sense anymore. |
17 |
|
18 |
One thing I forgot to mention, the x11-* would not go away just shrink. |
19 |
|
20 |
General stuff that is for say X11 or Wayland would go into the "new" |
21 |
categories. Anything that is X specific, like xorg, drivers, xephyr, etc |
22 |
would remain in the location and category it presently resides. |
23 |
|
24 |
This would reduce the amount of package moves, but still would be fair |
25 |
amount. With some being pretty major like moving GTK+. EFL ended up in |
26 |
dev-libs, and I am not sure if that is the proper location, though it |
27 |
does cross many categories. GTK+ and FLTK are in x11-libs. I think EFL |
28 |
ended up in dev-libs due to Wayland situation. |
29 |
|
30 |
P.S. |
31 |
I myself am not super excited about wayland. I see reliving a lot of |
32 |
the problems of the past. Not to mention wayland supporting what X can |
33 |
do now, today. Many things still in the works for most any |
34 |
supporting Wayland, dual display, different resolutions etc. I gave it |
35 |
a nickname "Waitland" as you have to WAIT for wayland to support this |
36 |
or that.... Either way it seems inevitable... Even if years off from |
37 |
being the daily driver. |
38 |
|
39 |
-- |
40 |
William L. Thomson Jr. |