Bug 66853

Summary:	weston-launch support specifing a binary path to another Wayland server
Product:	Wayland	Reporter:	nerdopolis1
Component:	weston	Assignee:	Wayland bug list <wayland-bugs>
Status:	RESOLVED MOVED	QA Contact:
Severity:	enhancement
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description nerdopolis1 2013-07-12 12:45:59 UTC

Hi.

Right now, weston-launch is only hard coded to launch weston.

I would really find an option to specify a path to another binary, with something such as weston-launch -b qtcompositor.

As there are other non weston compositors out there, not all of them ship with an equivilent of weston-launch that changes permissions as far as I'm aware.

Without much luck, I tried making a patch myself... http://pastebin.com/FRsK4DP6 but it doesn't work

Comment 1 nerdopolis1 2013-07-18 00:19:29 UTC

on IRC krh suggests that if this feature is added, weston-launch will need to have a config file that lists the executables/paths that weston-launch is permitted to run for security.

Comment 2 Daniel Stone 2013-08-21 13:59:51 UTC

fixed in master

Comment 3 nerdopolis1 2013-08-21 22:44:59 UTC

I don't think this was fixed? What commit? This is about specifying a path to another _Wayland_ server in the weston-launch arguments. (For a custom path to Weston)

Not an xwayland server in weston.ini

Comment 4 GitLab Migration User 2018-06-08 23:51:27 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/wayland/weston/issues/29.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.