From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Chris Larson <clarson@kergoth.com>
Subject: Re: [ANNOUNCE] Devshell Usage Change
Date: Wed, 24 Aug 2011 13:13:21 -0700 [thread overview]
Message-ID: <4E555B61.7030803@linux.intel.com> (raw)
In-Reply-To: <CABcZANn8NZYnA3dPzakgfMguaVV9EQ7isusAGMOQUQzHx_UV3w@mail.gmail.com>
On 08/24/2011 12:49 PM, Chris Larson wrote:
> Saul reminded me that I never sent a proper email to let people know about the
> usability change to devshell, so only those who reviewed the commits
> know about it.
>
> In the new implementation, a single OE_TERMINAL variable controls the behavior.
>
So your saying that the TERMCMD no longer works? We have to set both
TERMCMD and OE_TERMINAL?
That does not makes sense, If I set TERMCMD to use screen then it should
use screen, with out me having to also set OE_TERMINAL?
Or test TERMCMD go away at this point?
In either case, maybe we need to update the local.conf also.
Sau!
> When using 'auto', or requesting an unsupported terminal, we attempt to spawn
> them in priority order until we get one that's available on this system (and
> in the case of the X terminals, has DISPLAY defined). The 'none' value is
> used when we're doing things like automated builds, and want to ensure that no
> terminal is *ever* spawned, under any circumstances.
>
> Current available terminals (in addition to 'noop' and 'auto'):
>
> gnome
> konsole
> xterm
> rxvt
> screen
>
> Examples:
>
> OE_TERMINAL = "xterm"
> OE_TERMINAL = "noop"
next prev parent reply other threads:[~2011-08-24 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 19:49 [ANNOUNCE] Devshell Usage Change Chris Larson
2011-08-24 19:54 ` Khem Raj
2011-08-24 19:56 ` Chris Larson
2011-08-24 20:13 ` Saul Wold [this message]
2011-08-24 20:23 ` Khem Raj
2011-08-24 23:06 ` Chris Larson
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=4E555B61.7030803@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=clarson@kergoth.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.