openembedded-core.git/meta/classes/terminal.bbclass, branch dylan

classes/terminal: fix pseudo exiting when launching devshell

2013-08-16T09:39:41+00:00

In dylan, since the entire bitbake process is run under pseudo,
LD_PRELOAD is set when we collect BB_ORIGENV and thus when we construct
the devshell environment from the latter, LD_PRELOAD is included.
However, for a fakeroot task we explicitly run the devshell under pseudo
(e.g. "pseudo /bin/bash"), and if LD_PRELOAD is set to preload
libpseudo.so when pseudo is run, it seems to exit immediately without
error. Since LD_PRELOAD shouldn't be exported anyway, exclude this from
the environment so it doesn't prevent running the shell.

Signed-off-by: Paul Eggleton

terminal: Run command using a wrapper script

2013-08-07T10:44:32+00:00

Some terminals may not pass the environment into the child process. This
is true when using "tmux split-window." If tmux is already running, it
will start the command with the tmux session environment, ignoring the
environment where the command was issued.

This could possibly be worked around when launching tmux by injecting
variables into the user's session environment or adding the variables to
the "update-environment" tmux setting. However, both methods would
permanently alter the user's session, which is undesirable.

By using a wrapper script, we have full control over the final
environment. Replace the env dictionary with an empty data smart that
will contain the exported variables and a wrapper function that execs
the original command.

(From OE-Core master rev: 3bb96671e987ce8110ce98b9f6d9efc093f8d20e)

Signed-off-by: Tyler Hall 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

devshell.bbclass: Allow running devshell and fakeroot together

2013-02-19T16:36:54+00:00

Currently its hard to run a devshell complete with fakeroot context. This
patch allows the fakeroot flag on the task to do this, as with any other
task. Since we may need to start X terminal applications, we need to
only start the fakeroot session on the final command, hence the hoops
this code jumps through.

As always with fakeroot, you can break out and run a command without
the fake permissions with syntax like "PSEUDO_UNLOAD=1 "

[YOCTO #3374]

Signed-off-by: Richard Purdie 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

terminal.bbclass: Use BB_ORIGENV to restore user environmental variables

2013-02-06T23:40:22+00:00

Signed-off-by: Richard Purdie

terminal: Ensure existing environment exports are preserved in devshell

2012-11-02T11:27:43+00:00

After recent changes to terminal.bbclass, variables like PATH were no longer
preserved within the devshell. This change ensures they are inherited into
the environment of devshell and PATH for example has the correct values.

Signed-off-by: Richard Purdie

terminal.bbclass: Ensure parent environment is set

2012-11-01T11:49:13+00:00

If this isn't done, various terminals fail to launch correctly
with "No such file or directory" errors. This adds back the environment
manipulation removed in the addition of "custom" terminal command
support but shouldn't regress that additional functionality

Signed-off-by: Richard Purdie

terminal: Add support for running custom terminals.

2012-10-24T11:47:28+00:00

Example config:
OE_TERMINAL = "custom"
OE_TERMINAL_CUSTOMCMD = "mysuperterm"

Signed-off-by: Morten Minde Neergaard 
Signed-off-by: Saul Wold

terminal: pass data store all the way through to terminal class

2012-09-24T14:31:27+00:00

Passing the data store will be needed for firing a custom event
for the screen class.

Signed-off-by: Jason Wessel 
Signed-off-by: Richard Purdie

terminal.bbclass, oe-buildenv-internal: pass SCREENDIR environment variable

2012-05-06T08:54:45+00:00

Some versions of the screen utility provided from the host OS vendor
write the socket directory to $HOME/.screen.  When using a shared home
directory across many servers, one sets the SCREENDIR environment
variable to avoid collisions in the shared home directory.  This
results in problems launching a devshell where it is not entirely
obvious what happened because the SCREENDIR environment variable
got stripped from the environment prior to setting up the screen
in detached mode.

Example:
   % bitbake -c devshell busybox
   # ...Please connect in another terminal with "screen -r devshell"

   % screen -r devshell
   There is no screen to be resumed matching devshell.

The temporary work around was to do something like:
   sh -c "unset SCREENDIR; screen -r devshell"

This patch adds SCREENDIR to the white list to ensure screen
works properly on systems where a developer needs to use
the SCREENDIR with shared home directories.

Signed-off-by: Richard Purdie

terminal.bbclass: Improve environment handling

2011-09-09T17:39:12+00:00

Currently the environment handling for terminals is inconsistent. There
are two fixes here:

a) Ensure the environment is setup before all oe.terminal call

b) Actually set the environment before the spawn calls since we need
variables like DISPLAY when the commands are being executed, not just
within the terminal environment. If this doesn't happen, DISPLAY can end
up not set with the errors that brings with it when trying to run X
commands.

Signed-off-by: Richard Purdie