openembedded-core.git/scripts/lib/devtool, branch uninative-1.3

devtool: add finish subcommand

2016-07-20T09:24:53+00:00

Add a subcommand which will "finish" the work on a recipe. This is
effectively the same as update-recipe followed by reset, except that the
destination layer is required and it will do the right thing depending
on the situation - if the recipe file itself is in the workspace (e.g.
as a result of devtool add), the recipe file and any associated files
will be moved to the destination layer; or if the destination layer is
the one containing the original recipe, the recipe will be overwritten;
otherwise a bbappend will be created to apply the changes. In all cases
the layer path can be loosely specified - it could be a layer name, or
a partial path into a recipe. In the case of upgrades, devtool finish
will also take care of deleting the old recipe.

This avoids the user having to figure out the correct actions when
they're done - they just do "devtool finish recipename layername" and
it saves their work and then removes the recipe from the workspace.

Addresses [YOCTO #8594].

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

devtool: upgrade: record original recipe files

2016-07-20T09:24:53+00:00

This provides us with the information we need to remove the original
version recipe and associated files when running "devtool finish" after
"devtool upgrade".

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

devtool: update-recipe: refactor to allow calling separately

2016-07-20T09:24:53+00:00

This will be called by "devtool finish" to allow it to update the recipe
or create the bbappend depending on the destination.

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

devtool: reset: refactor to allow calling separately

2016-07-20T09:24:53+00:00

This will be called by "devtool finish" to allow it to reset the recipe
at the end.

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

devtool: update-recipe: don't copy local files that haven't changed

2016-07-20T09:24:53+00:00

If there are files in the oe-local-files directory which are identical
to the original version, then we shouldn't be copying them to the
destination layer. This is particularly important when using the -a
option to create a bbappend.

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

devtool: update-recipe: find and use existing files directories

2016-07-20T09:24:53+00:00

devtool update-recipe was defaulting to the ${BPN} named directory when
adding patches next to a recipe, but that meant if you already had files
in a ${BP} named directory (i.e. name and version) or "files" then you'd
end up with two directories next to the recipe, which is usually not
what you want. To avoid this, look through FILESPATH and take the first
one that's the same level or one level down from the recipe and already
exists, if any.

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

recipetool: create: support specifying a file as the local source

2016-07-12T22:10:04+00:00

It is currently possible to specify a file (e.g. a tarball) on the local
disk as the source, but you have to know to put file:// in front of it.
There's really no need to force users to jump through that hoop if they
really want to do this so check if the specified source is a file and
prefix it with file:// if that's the case.

Also ensure the same works for "devtool add" at the same time.

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

devtool: return specific exit code for incompatible recipes

2016-07-12T22:10:04+00:00

Certain recipes cannot be used with devtool extract / modify / upgrade -
usually because they don't provide any source. Return a specific exit
code (4) so that scripts such as scripts/contrib/devtool-stress.py know
the difference between this and a genuine failure.

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

devtool: reset: allow reset to work if the recipe file has been deleted

2016-07-12T22:10:04+00:00

We were attempting to open the recipe file unconditionally here - we
need to account for the possibility that the recipe file has been
deleted or moved away by the user.

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

devtool: update-recipe: fix --initial-rev option

2016-07-12T22:10:04+00:00

In OE-Core revision 7baf57ad896112cf2258b3e2c2a1f8b756fb39bc I changed
the default update-recipe behaviour to only update patches for commits
that were changed; unfortunately I failed to handle the --initial-rev
option which was broken after that point. Rework how the initial
revision is passed in so that it now operates correctly.

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