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

recipetool: create: fix greedy regex that broke support for github tarballs

2016-07-28T20:30:16+00:00

The regex here needs to be anchored to the end or it'll match longer
URLs, which was exactly what I was trying to avoid. This regression was
introduced in OE-Core revision 7998dc3597657229507e5c140fceef1e485ac402.

Fixes [YOCTO #10023].

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

recipetool: record unknown license files

2016-07-25T22:47:03+00:00

Add a comment to the recipe listing license files that were found but
not able to be identified, so that the user can find and examine them
by hand fairly easily.

Fixes [YOCTO #9882].

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

wic: rawcopy: make source filenames unique

2016-07-21T06:45:01+00:00

Rawcopy plugin copies source files to build folder before using them
to assemble result image. After assembling the image wic renames
source files to .p. If the same source file
is used in multiple partitions wic breaks trying to rename file that
doesn't exist.

Added  suffix to the files when copying them to the
build dir. This should make filename unique even if the same source
file is used for multiple partitions.

[YOCTO #9826]

Signed-off-by: Ed Bartosh 
Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie

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

wic: mountpoint is an optional argument

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

According to wic documentation partition mount point is an optional
argument. Skipping mount point also makes sense in certain
configurations when one needs to specify a partition that is not mounted
by the running system, such as a recovery or a mirror partition (in dual
rootfs setups).

Signed-off-by: Maciej Borzecki 
Signed-off-by: Ross Burton