After setting TEMPLATECONF="$PWD/whatever" to make sure the path is correct, I get the following message when attempting to install the ext-sdk produced: Error: TEMPLATECONF value points to nonexistent directory "/path/on/ci/server/..." This path seems to be written as-is to templateconf.cfg, I see several possibilities: - transform into a relative path before writing to templateconf.cfg - warn that ext-sdk will be broken and proceed - bomb out from the very beginning
Looking at the code its hard to tell what is supported in that. I suspect the eSDK needs to be taught some kind of relocation...
oe-setup-builddir interprets the TEMPLATECONF path as relative to the builddir (which is not yet created at the time the user has to specify it) but also supports $OEROOT-relative paths. Would it be correct to assume that $OEROOT-relative paths are what is really supported and ought to be documented, and that builddir-relative is probably a side-effect or old compat mode ? Given the existence of those, how could we introduce standard-looking and more intuitiv $PWD-relative paths ?
Bulk move of 64 bugs to 4.3 M3 after a quick review. If a bug is actually fixed, please add a commit link and resolve it. -- Randy for YP bug team.
Moved to M4.
Bulk move to 5.0 M1. -- Randy
Bulk move of 52 5.0-M1 bugs to M2.
Bulk move of bugs owned by "unassigned" from 5.0-M2 to 5.0-M3.
Bulk move of bugs from 5.0-M3 to 5.99. The bugs in this list are all unassigned and are ones that I consider to be nice to do some time but not essential track from milestone to milestone in 5.0 or 5.1. We agreed on this bug handling approach in the YP bug review on Feb 22, 2024. If you disagree, please move back to a 5.[012...]-M* milestone.
The extensible SDK subsystem still needs work but few users seem to notice. Move to 6.99 as a holding milestone.