openembedded-core.git/scripts/devtool, branch krogoth

devtool: Fix build-sdk when pn doesn't match filename

2016-05-17T20:28:32+00:00

If an image with the filename foo.bb could be built using the name "bar"
instead, then build-sdk would fail to create the derivative sdk.

This was because the code assumed that the file name matched the target,
which is not necessarily the case.

(From OE-Core rev: d58a326b6960be14b8a049253559aec9582b7d0d)

Signed-off-by: Randy Witt 
Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie 
Signed-off-by: Armin Kuster 
Signed-off-by: Richard Purdie

devtool: Create unlocked-sigs.inc containing items in the workspace

2016-04-08T06:53:09+00:00

When a recipe is added to the workspace, the signatures for the tasks
will change. This means that bitbake must be told to allow the
signatures to be different if they are in locked-sigs.inc.

This is done by creating an unlocked-sigs.inc file which contains all
the recipes in the workspace each time devtool reads the workspace.

So not only will necessary things get added, previously added items will
be removed by virtue of them no longer being in the workspace.

This also makes sure that the extensible sdk picks up unlocked-sigs.inc
as part of the configuration.

[YOCTO #9195]

Signed-off-by: Randy Witt 
Signed-off-by: Richard Purdie

scripts, lib: Don't limit traceback lengths to arbitrary values

2016-03-31T12:18:12+00:00

There appears to have been a lot of copy and pasting of the code
which prints tracebacks upon failure and limits the stack trace to
5 entries. This obscures the real error and is very confusing to the user
it look me an age to work out why some tracebacks weren't useful.

This patch removes the limit, making tracebacks much more useful for
debugging.

[YOCTO #9230]

Signed-off-by: Richard Purdie

devtool: categorise and order subcommands in help output

2016-02-21T09:32:00+00:00

The listing of subcommands in the --help output for devtool was starting
to get difficult to follow, with commands appearing in no particular
order (due to some being in separate modules and the order of those
modules being parsed). Logically grouping the subcommands as well as
being able to exercise some control over the order of the subcommands
and groups would help, if we do so without losing the dynamic nature of
the list (i.e. that it comes from the plugins). Argparse provides no
built-in way to handle this and really, really makes it a pain to add,
but with some subclassing and hacking it's now possible, and can be
extended by any plugin as desired.

To put a subcommand into a group, all you need to do is specify a group=
parameter in the call to subparsers.add_parser(). you can also specify
an order= parameter to make the subcommand sort higher or lower in the
list (higher order numbers appear first, so use negative numbers to
force items to the end if that's what you want). To add a new group, use
subparsers.add_subparser_group(), supplying the name, description and
optionally an order number for the group itself (again, higher numbers
appear first).

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

devtool: Don't recursively look for .devtoolbase in --basepath

2016-02-21T09:31:58+00:00

If the user specifies --basepath on the commandline, only the directory
specified should be searched for .devtoolbase. Otherwise when --basepath
is a child of the sdk directory, .devtoolbase will always be found and
devtool will only show options meant to be used within an sdk.

Signed-off-by: Randy Witt 
Signed-off-by: Richard Purdie

devtool: refactor code for getting local recipe file

2016-01-11T15:41:07+00:00

We're doing this in a couple of places, let's just find the recipe file
if it exists within the workspace (which it will if it's been added
through "devtool add") when we read in the workspace.

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

devtool: modify: default source tree path

2015-12-22T16:44:03+00:00

As per the changes to "devtool add", make the source tree path optional
and use the default path if none is specified.

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

devtool: add: allow specifying URL as positional argument

2015-12-22T16:44:03+00:00

Having to specify -f is a little bit ugly when a URI is distinctive
enough to recognise amongst the other positional parameters, so take it
as an optional positional parameter. -f/--fetch is still supported, but
deprecated.

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

scripts: print usage in argparse-using scripts when a command-line error occurs

2015-12-22T16:44:02+00:00

For scripts that use Python's standard argparse module to parse
command-line arguments, create a subclass which will show the usage
the usage information when a command-line parsing error occurs. The most
common case would be when the script is run with no arguments; at least
then the user immediately gets to see what arguments they might need to
pass instead of just an error message.

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

devtool: clarify help text

2015-12-01T21:30:55+00:00

* Make some minor clarifications to help text
* Drop ArgumentDefaultsHelpFormatter and just put the defaults in the
  text itself where needed (because otherwise you get defaults shown for
  store_true options which is somewhat confusing).

Signed-off-by: Paul Eggleton 
Signed-off-by: Ross Burton