Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Tom Hochstein <Tom.Hochstein@freescale.com>
Cc: Sundararaj Prabhu <Prabhu.Sundararaj@freescale.com>,
	Otavio Salvador <otavio.salvador@ossystems.com.br>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] weston-init: Use weston-launch for XWayland
Date: Fri, 11 Dec 2015 14:29:40 +0200	[thread overview]
Message-ID: <566AC1B4.9050508@linux.intel.com> (raw)
In-Reply-To: <BN3PR03MB1415A9FC4E4B3D1B7773F618E8E90@BN3PR03MB1415.namprd03.prod.outlook.com>

On 12/11/2015 01:44 AM, Tom Hochstein wrote:

>          # There are multiple ways to start weston.
>          if [ "$WAYLAND_DISPLAY" ]; then
>              echo -e "\aError: Weston is already running."
>              echo "This script does not support launching Weston nested."
>              exit 1
>          else if [ "$DISPLAY" ]; then
>              echo "Launching Weston with the x11 backend"
>              openvt -s weston -- --log=/var/log/weston.log $OPTARGS
>          else
>              echo "Launching Weston with the DRM backend"
>              export XDG_CONFIG_HOME=/etc
>              openvt -v -- weston-launch -- --log=/var/log/weston.log $OPTARGS
>          fi
>
> I still need to test this (and apply the design in systemd), but I wanted your feedback on the approach.

I think this looks okay, but you obviously need to test that all three 
scenarios works as expected. Also, systemd unit file language may not 
support this logic (it's not a full programming language), so the above 
snippet probably needs to be separated into a wrapper script.

Alex



  reply	other threads:[~2015-12-11 12:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 20:31 [PATCH v2] weston-init: Use weston-launch for XWayland Tom Hochstein
2015-12-01 22:21 ` alexander.kanavin
2015-12-07 13:19   ` Tom Hochstein
2015-12-07 14:13     ` Otavio Salvador
2015-12-07 14:18       ` Alexander Kanavin
2015-12-10 23:44         ` Tom Hochstein
2015-12-11 12:29           ` Alexander Kanavin [this message]
2015-12-11 12:34             ` Otavio Salvador

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=566AC1B4.9050508@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=Prabhu.Sundararaj@freescale.com \
    --cc=Tom.Hochstein@freescale.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox