DESCRIPTION: The yocto-compat-layer-wrapper does not pass down the option -o to the yocto-compat-layer.py since the log is not created. Also the yocto-compat-layer-wrapper calls on to source the oe-init-build-env every time you run it. this is confusing since to be able to run this command I required to source oe-init-build-env before hand. ENVIRONMENT SETUP: 1. commit 3e655f9c7f0f4f778dc9eedd9f7405fc84b4c9ad 2. Laptop OS ---> Debian 4.3.5-1~bpo8+1 STEPS TO REPRODUCE: 1. clone poky from git 2. source oe-init-build-env build 3. yocto-compat-layer-wrapper LAYER_DIR ../meta-extras/ -o error.log 4. ls to see if the error.log file was created. No error log created 5. yocto-compat-layer-wrapper -o error.log LAYER_DIR ../meta-extras/ 6. ls to see if the error.log file was created. No error log created 7. yocto-compat-layer.py LAYER_DIR ../meta-extras/ -o error.log 8. ls error.log file was created successfully. OUTPUT EXPECTED: since yocto-compat-layer-wrapper passes the values and calls internally yocto-compat-layer.py. I expected both scripts to give the same output and act the same. When running yocto-compat-layer-wrapper like in step 3 and 5 it sources again the oe-init-build-env. When running the yocto-compat-layer.py like in step 7 it does not source the oe-init-build-env Its confusing to have yocto-compat-layer-wrapper run the source every time you run it including when ran with the --help option.
Review at, http://lists.openembedded.org/pipermail/openembedded-core/2017-June/137576.html
Merge at, http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=24b7e71350316d81e0f7eb5c11e2d5014adfd50f