| Summary: |
devtool: new recipe addition still keeps using the previous recipes variables in the new one |
| Product: |
[Build System, Metadata & Runtime] OE-Core
|
Reporter: |
Shan Desai <shantanoo_desai> |
| Component: |
devtools / tool chain | Assignee: |
Shan Desai <shantanoo_desai> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium+
|
CC: |
meta.mr.watcher, meta.watcher, randy.macleod
|
| Version: |
unspecified | |
|
| Target Milestone: |
3.2 M4 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
## System Build Host: Debian 9 Stretch Target Hardware: PHYTEC PhyBOARD Mira - iMX6 Quad Board Open-Embedded branch: warrior Bitbake Version: 1.42.0 ## Initial Setup - I ported my python3 app using the following command using `devtool`: devtool add python3-gpsfluxlite <github archive tarball> which create the recipe for me in my $BUILDDIR/workspace/recipes/python3-gpsfluxlite - I only changed the `RDEPENDS_${PN}` from `python-depname` to `${PYTHON_PN}-depname` in the recipe and added `systemd` installation script for the app. - The build was successful and I wrapped up the recipe in my layer using `devtool reset python3-gpsfluxlite` && `devtool finish python3-gpsfluxlite ../to/my/layer` and it worked well ## Problem - I wish to port another python3 app and I followed the same development workflow as above: devtool add python3-bnofluxlite <github archive tarball> This time the Terminal kept mentioning the packages and dependencies still from gpsfluxlite (see logs): INFO: Scanning paths for packages & dependencies: gpsinfluxlite, bin/gpsinfluxlite - upon editing the recipe `devtool edit-recipe python3-bnofluxlite` I still see remnants from the `gpsfluxlite` recipe (Pastebin link: https://pastebin.com/KmyENMRh of generated recipe) e.g. `S = "${WORKDIR}/gpsfluxlite-${PV}"` as well the `RDEPENDS` from the previous recipe. The only workaround is to clean up the workspace and use `--srcrev` with `devtool add` to generate the correct recipe. Seems like `devtool` isn't picking up or changing the downloaded tarball