From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH (v2,resend) 0/3] Rework the devshell
Date: Thu, 19 May 2011 17:02:58 -0700 [thread overview]
Message-ID: <1305849778.9983.29.camel@vorpal.jf.intel.com> (raw)
In-Reply-To: <cover.1305737923.git.chris_larson@mentor.com>
On Wed, 2011-05-18 at 10:17 -0700, Chris Larson wrote:
> From: Chris Larson <chris_larson@mentor.com>
>
> - Adds a utility metaclass for maintaining class registries
> - Shifts the handling of spawning a terminal into a new 'terminal' python
> module
> - Automatically selects an appropriate terminal based on what you have
> available on your machine
> - Still allows manual selection, but in a more convenient way, and falls back
> to auto if you select an invalid or unavailable (not installed) terminal
> - Improves how we spawn screen:
>
> - Shows a warning when spawning it, so do_devshell doesn't appear to hang
> - Spawns a named screen session 'devshell', to avoid confusion when the user
> already has other screen sessions running
>
> Example usage of the new API for others (e.g. patch resolver) to use:
>
> import oe.terminal
> oe.terminal.run(command, terminal_title, d)
>
> Pull URL: git://git.openembedded.org/openembedded-core-contrib
> Branch: kergoth/devshell
> Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kergoth/devshell
>
> Thanks,
> Chris Larson <chris_larson@mentor.com>
I like this series!
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....).
Perhaps we should remove support for it from the class? Or is there some
better way we can work around this?
As an aside: I think somewhere in meta-yocto, to maintain current
behaviour we'd want to set: OE_TERMINAL ?= 'Gnome' to maintain
gnome-terminal as the default (when installed).
Acked-by: Joshua Lock <josh@linux.intel.com>
Cheers,
Joshua
> ---
>
>
> Chris Larson (3):
> oe.classutils: add module
> Rework how the devshell functions
> oe.terminal: improve how we spawn screen
>
> meta/classes/devshell.bbclass | 25 ++------
> meta/conf/bitbake.conf | 9 +++
> meta/lib/oe/classutils.py | 45 ++++++++++++++
> meta/lib/oe/terminal.py | 131 +++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 191 insertions(+), 19 deletions(-)
> create mode 100644 meta/lib/oe/classutils.py
> create mode 100644 meta/lib/oe/terminal.py
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Joshua Lock
Yocto Project Build Monkey
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-05-20 0:02 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 ` Joshua Lock [this message]
2011-05-20 10:09 ` [PATCH (v2,resend) 0/3] Rework the devshell Paul Eggleton
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=1305849778.9983.29.camel@vorpal.jf.intel.com \
--to=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