1 |
On Wed, Dec 21, 2016 at 02:04:05PM -0500, Rich Freeman wrote: |
2 |
> On Wed, Dec 21, 2016 at 1:44 PM, <Meino.Cramer@×××.de> wrote: |
3 |
> > Corbin Bird <corbinbird@×××××××.net> [16-12-21 17:12]: |
4 |
> > The first run of emerge tells me to add the systemd USE flag to dbus. |
5 |
> > I did that and ran into to problems I reported. |
6 |
> |
7 |
> Ok, I think you left that bit out... |
8 |
> |
9 |
> And this is why it is helpful to understand why portage is doing |
10 |
> something before just changing configuration settings. Adding the |
11 |
> systemd USE flag to packages is a really quick way to end up with |
12 |
> systemd getting installed. Generally speaking it shouldn't just |
13 |
> happen by default... |
14 |
> |
15 |
> Can you show the output when you add -t to the emerge command? I |
16 |
> think that will be helpful. However, I think an earlier poster was on |
17 |
> the right track when he pointed out that the tmpfiles virtual requires |
18 |
> an unstable version of openrc. I'm not sure why that was getting |
19 |
> pulled in in the first place, and -t should show that. |
20 |
> |
21 |
> > |
22 |
> > emerge: there are no ebuilds built with USE flags to satisfy "media-libs/mesa[egl,gbm,gles2?,wayland]". |
23 |
> > !!! One of the following packages is required to complete your request: |
24 |
> > - media-libs/mesa-11.2.2::gentoo (Change USE: +wayland) |
25 |
> > (dependency required by "kde-plasma/kwin-5.8.3::gentoo" [ebuild]) |
26 |
> > (dependency required by "kde-plasma/plasma-workspace-5.8.3-r4::gentoo" [ebuild]) |
27 |
> > (dependency required by "net-p2p/ktorrent-5.0.1::gentoo[shutdown]" [ebuild]) |
28 |
> > (dependency required by "@selected" [set]) |
29 |
> > (dependency required by "@world" [argument]) |
30 |
> > [1] 20322 exit 1 emerge -t --update --newuse --deep --with-bdeps=y --tree --keep-going |
31 |
> > |
32 |
> > What? |
33 |
> > |
34 |
> > Now wayland shall be installed? IIIIIKKKKKSSSS! |
35 |
> > I want my UNIX back! |
36 |
> |
37 |
> Interesting. I just noticed that it pulled in wayland for me. I have |
38 |
> no idea why kwin requires wayland support in mesa. It obviously works |
39 |
> fine with xorg. I might do some looking into that. |
40 |
> |
41 |
> There isn't really anything non-UNIX about wayland, though I'm not |
42 |
> sure I'd be in a rush to use it just yet. It is just a replacement |
43 |
> for xorg (to say the least, it doesn't purport to be a |
44 |
> feature-complete replacement and may never be). |
45 |
|
46 |
Wayland may not be non-UNIX, but putting everything into the compositor |
47 |
(including keyboard input) just shifts responsibility to another piece |
48 |
of software and actually complicates things a bit. I've not done much |
49 |
digging into the matter but if I understood the structure of Wayland |
50 |
correctly, you can't take screenshots or other talks-to-display-server |
51 |
stuff unless the compositor supports it. With so much I/O going through |
52 |
one thing (the compositor), it's ripe for abuse and security problems. |
53 |
|
54 |
Of course, that doesn't make Xorg's security problems go away... like |
55 |
any other set of competing software, you're trading one set of pros/cons |
56 |
for another. |
57 |
|
58 |
I've not seen anything about Wayland that convinces me it's hands-down |
59 |
better. |
60 |
|
61 |
That plasma dependency sounds weird, though. If you're not using |
62 |
Wayland, it shouldn't require mesa to support it. |
63 |
|
64 |
> |
65 |
> Your wayland issues and your systemd issues are most likely entirely |
66 |
> unrelated... |
67 |
> |
68 |
> -- |
69 |
> Rich |
70 |
> |