Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Patches and discussions about the oe-core layer"
	<openembedded-core@lists.openembedded.org>,
	 Joshua Lock <josh@linux.intel.com>
Subject: Re: [PATCH (v2,resend) 0/3] Rework the devshell
Date: Fri, 20 May 2011 11:09:49 +0100	[thread overview]
Message-ID: <201105201109.50052.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <1305849778.9983.29.camel@vorpal.jf.intel.com>

On Friday 20 May 2011 01:02:58 Joshua Lock wrote:
> Speaking of devshell, last I tried (and Paul E can correct me here)
> Konsole doesn't wait when it's spawned so is currently pretty useless
> for devshell (bitbake continues as if the devshell had finished and if a
> patch hasn't applied....).

I can confirm this - right now our Konsole support just does not work and I 
imagine it has not since KDE 4.0. Adding the --nofork command line option 
which is supposed to make it wait does not work either, because if the 
controlling terminal is not interactive it assumes there is no other instance 
of Konsole running, tries to register a DBUS service and fails (and it's hard 
to imagine someone using KDE and running bitbake without having an instance of 
Konsole running already).
 
> Perhaps we should remove support for it from the class? Or is there some
> better way we can work around this?

A while ago I had a look adding a command line option to Konsole itself to 
make this work but didn't get very far, although I don't think it should be 
too difficult. There is a workaround script [1] but when I tried it just now I 
found it again has problems if the controlling terminal is not interactive 
(never returns). Frankly the script is hideous and maybe it was broken in a 
version of KDE since the script was written, I don't know.

It might be prudent to remove the Konsole support until it has been fixed 
appropriately; at the very least it should be documented to only work with 
Konsole from KDE 3.x.

FYI the "workaround" I use here for the moment (if I don't just disable the 
feature with PATCHRESOLVE = "noop") is to use xterm instead of Konsole for 
TERMCMD and TERMCMDRUN.

Cheers,
Paul

[1] http://lists.kde.org/?l=kde-core-devel&m=123188146810950&w=2



      reply	other threads:[~2011-05-20 10:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 17:17 [PATCH (v2,resend) 0/3] Rework the devshell Chris Larson
2011-05-18 17:17 ` [PATCH (v2,resend) 1/3] oe.classutils: add module Chris Larson
2011-05-18 17:18 ` [PATCH (v2, resend) 2/3] Rework how the devshell functions Chris Larson
2011-05-18 17:18 ` [PATCH (v2, resend) 3/3] oe.terminal: improve how we spawn screen Chris Larson
2011-05-20  0:02 ` [PATCH (v2,resend) 0/3] Rework the devshell Joshua Lock
2011-05-20 10:09   ` Paul Eggleton [this message]

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=201105201109.50052.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=josh@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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