summaryrefslogtreecommitdiffstats
path: root/scripts/bitbake-whatchanged
diff options
context:
space:
mode:
authorPatrick Ohly <patrick.ohly@intel.com>2015-03-27 14:53:10 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-03-31 22:24:34 +0100
commitd81ee4d2770144e9b4507ee3836599e77a07b2ea (patch)
tree1f6b27a3f787656e3a082583e7c29aa7c62afac5 /scripts/bitbake-whatchanged
parent232ccf23cf5ab9e39f859539ab3d823e2631e431 (diff)
downloadast2050-yocto-poky-d81ee4d2770144e9b4507ee3836599e77a07b2ea.zip
ast2050-yocto-poky-d81ee4d2770144e9b4507ee3836599e77a07b2ea.tar.gz
combo-layer: clean up dest_dir checking
Empty dest_dir is basically undocumented behavior. The sample conf only mentions using just a dot for the current directory. In practice, the empty string does not work because of code like this: def action_splitpatch(conf, args): ... if dest_dir != ".": filerange_root = '%s -x "%s/*"' % (filerange_root, dest_dir) However, the empty string was not explicitly checked for, leading to strange errors when trying to apply patches: [12:50:23] Applying: foobar: xyz fatal: unable to stat newly created file '/foobar': No such file or directory This patch turns the empty string into an alias for the dot. This seems more user-friendly than throwing an error. This alias is intentionally not document in the sample conf, because the dot is clearer and works also with older copies of combo-layer. Instead of checking for both all the time and normalizing the path when needed (as done in some places), rewrite the value in sanity_check() and then only check for '.'. (From OE-Core rev: a8547b3c2c0b8bf3150043b1b6570f0d44b20335) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/bitbake-whatchanged')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud