launchers: remove launchers

Moving forward we're going to be supporting libseat and logind as our
only launchers. We're doing this to reduce our maintenance burden,
and security impact.

Libseat supports all our existing use cases, and seatd can replace
weston-launch so we no longer have to carry a setuid-root program.

This patch removes weston-launch, and launcher-direct, leaving only
libseat and logind.

Signed-off-by: Derek Foreman <derek.foreman@collabora.com>

man/weston-bindings.man

@@ -165,7 +165,6 @@ Enable repaint debugging for pixman:
 
 .SH "SEE ALSO"
 .BR weston (1),
-.BR weston-launch (1),
 .BR weston-drm (7),
 .BR weston.ini (5),
 .BR xkeyboard-config (7)

man/weston-drm.man

@@ -2,8 +2,6 @@
 .SH NAME
 weston-drm \- the DRM backend for Weston
 .SH SYNOPSIS
-.B weston-launch
-.LP
 .B weston --backend=drm-backend.so
 .
 .\" ***************************************************************
@@ -33,19 +31,6 @@ the first DRM device returned by
 .BR udev (7).
 Combining multiple graphics devices is not supported yet.
 
-The DRM backend relies on
-.B weston-launch
-for managing input device access and DRM master status, so that
-.B weston
-can be run without root privileges. On switching away from the
-virtual terminal (VT) hosting Weston, all input devices are closed and
-the DRM master capability is dropped, so that other servers,
-including
-.BR Xorg (1),
-can run on other VTs. On switching back to Weston's VT, input devices
-and DRM master are re-acquired through the parent process
-.BR weston-launch .
-
 The DRM backend also supports virtual outputs that are transmitted over
 an RTP session as a series of JPEG images (RTP payload type 26) to a remote
 client. Virtual outputs are configured in the
@@ -218,23 +203,10 @@ The minimum libinput verbosity level to be printed to Weston's log.
 Valid values are
 .BR debug ", " info ", and " error ". Default is " info .
 .TP
-.B WESTON_TTY_FD
-The file descriptor (integer) of the opened tty where
-.B weston
-will run. Set by
-.BR weston-launch .
-.TP
-.B WESTON_LAUNCHER_SOCK
-The file descriptor (integer) where
-.B weston-launch
-is listening. Automatically set by
-.BR weston-launch .
-.TP
 .B XDG_SEAT
 The seat Weston will start on, unless overridden on the command line.
 .
 .\" ***************************************************************
 .SH "SEE ALSO"
 .BR weston (1)
-.\".BR weston-launch (1),
 .\".BR weston.ini (5)

man/weston.ini.man

@@ -482,10 +482,7 @@ currently only recognized by the drm and x11 backends.
 .BI "name=" name
 sets a name for the output (string). The backend uses the name to
 identify the output. All X11 output names start with a letter X.  All
-Wayland output names start with the letters WL.  The available
-output names for DRM backend are listed in the
-.B "weston-launch(1)"
-output.
+Wayland output names start with the letters WL.
 Examples of usage:
 .PP
 .RS 10

man/weston.man

@@ -17,14 +17,6 @@ Weston supports fundamentally different graphical user interface paradigms via
 shell plugins. Two plugins are provided: the desktop shell, and the tablet
 shell.
 
-When weston is started as the first windowing system (i.e. not under X nor
-under another Wayland server), it should be done with the command
-.B weston-launch
-to set up proper privileged access to devices. If your system supports
-the logind D-Bus API and the support has been built into weston as well,
-it is possible to start weston with just
-.BR weston .
-
 Weston also supports X clients via
 .BR XWayland ", see below."
 .
@@ -361,9 +353,9 @@ http://wayland.freedesktop.org/
 .\" ***************************************************************
 .SH EXAMPLES
 .IP "Launch Weston with the DRM backend on a VT"
-weston-launch
+weston
 .IP "Launch Weston with the DRM backend and XWayland support"
-weston-launch -- --xwayland
+weston --xwayland
 .IP "Launch Weston (wayland-1) nested in another Weston instance (wayland-0)"
 WAYLAND_DISPLAY=wayland-0 weston -Swayland-1
 .IP "From an X terminal, launch Weston with the x11 backend"