* [ANNOUNCE] Devshell Usage Change
@ 2011-08-24 19:49 Chris Larson
2011-08-24 19:54 ` Khem Raj
2011-08-24 20:13 ` Saul Wold
0 siblings, 2 replies; 6+ messages in thread
From: Chris Larson @ 2011-08-24 19:49 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
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.
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"
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphi
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [ANNOUNCE] Devshell Usage Change
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
1 sibling, 1 reply; 6+ messages in thread
From: Khem Raj @ 2011-08-24 19:54 UTC (permalink / raw)
To: openembedded-core
On 8/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.
>
> 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
is it 'none' or 'noop' ?
> 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"
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ANNOUNCE] Devshell Usage Change
2011-08-24 19:54 ` Khem Raj
@ 2011-08-24 19:56 ` Chris Larson
0 siblings, 0 replies; 6+ messages in thread
From: Chris Larson @ 2011-08-24 19:56 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Wed, Aug 24, 2011 at 12:54 PM, Khem Raj <raj.khem@gmail.com> wrote:
> On 8/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.
>>
>> 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
>
> is it 'none' or 'noop' ?
Erm, yes, none is correct. Thanks.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ANNOUNCE] Devshell Usage Change
2011-08-24 19:49 [ANNOUNCE] Devshell Usage Change Chris Larson
2011-08-24 19:54 ` Khem Raj
@ 2011-08-24 20:13 ` Saul Wold
2011-08-24 20:23 ` Khem Raj
2011-08-24 23:06 ` Chris Larson
1 sibling, 2 replies; 6+ messages in thread
From: Saul Wold @ 2011-08-24 20:13 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer; +Cc: Chris Larson
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"
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ANNOUNCE] Devshell Usage Change
2011-08-24 20:13 ` Saul Wold
@ 2011-08-24 20:23 ` Khem Raj
2011-08-24 23:06 ` Chris Larson
1 sibling, 0 replies; 6+ messages in thread
From: Khem Raj @ 2011-08-24 20:23 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer; +Cc: Chris Larson
On 8/24/2011 1:13 PM, Saul Wold wrote:
> 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?
I think so using OE_TERMINAL should suffice
>
> In either case, maybe we need to update the local.conf also.
yes
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ANNOUNCE] Devshell Usage Change
2011-08-24 20:13 ` Saul Wold
2011-08-24 20:23 ` Khem Raj
@ 2011-08-24 23:06 ` Chris Larson
1 sibling, 0 replies; 6+ messages in thread
From: Chris Larson @ 2011-08-24 23:06 UTC (permalink / raw)
To: Saul Wold; +Cc: Patches and discussions about the oe-core layer
On Wed, Aug 24, 2011 at 1:13 PM, Saul Wold <sgw@linux.intel.com> wrote:
> 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.
At the moment, TERMCMD affects the patch reject resolver, but only
because it hasn't been updated to use the new code yet. TERMCMD is
*not* used by the new code, and setting has absolutely no effect for
devshell usage.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2011-08-24 23:11 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2011-08-24 20:23 ` Khem Raj
2011-08-24 23:06 ` Chris Larson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox