Not according to their documentation:
* the weston launcher program (weston-launch) needs extra privileges to
issue the KMS ioctl()s. It can do so via systemd, or you can make
weston-launch setuid root.
* weston can use systemd to find the directory in which to put its control
socket, or you can set the environment variable $XDG_RUNTIME_DIR in your
shell before running it.

Source: http://wayland.freedesktop.org/building.html

I still need to figure out whether or not it needs runtime linkage against
systemd infrastructure, however. Fortunately, the Wayland developers
standardized the wayland protocol separately from the implementation, so at
worst we can fork weston or write our own compositor if systemd integration
becomes too troublesome to work around.

-Jude

On Sun, Feb 22, 2015 at 10:43 AM, Steve Litt <slitt@???>
wrote:

> On Sun, 22 Feb 2015 06:22:03 -0600
> hal <vmlinux@???> wrote:
>
> > Jaromil wrote on 02/22/15 04:28:
> > > At the very least, we may want to make sure that people is still
> > > free to choose between wayland and X11, but hopefully this will be
> > > also something that Debian wants.
> > >
> > >
> > >
> https://git.gnome.org/browse/gdm/commit/?id=ab90bd38c5cf2236c3527cf7ef6b9f383218a9e5
> > >
> >
> > At first I thought this was Gnome doing something stupid. Then I
> > realized it was just Redhat hard at work Poetterizing something.
>
> Isn't Wayland so systemd encumbered that somebody's going to need to
> write an alternative?
>
> SteveT
>

> Steve Litt                *  http://www.troubleshooters.com/
> Troubleshooting Training  *  Human Performance

>
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>