Bug 14098

Summary:	absolute path in TEMPLATECONF should be rejected or warned, makes ext-sdk uninstallable
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Yann Dirson <ydirson>
Component:	Scripts and Tools	Assignee:	Unassigned <unassigned>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	Medium+	CC:	ccasciato, randy.macleod, richard.purdie, ross.burton, tgamblin
Version:	unspecified
Target Milestone:	6.99
Hardware:	x86
OS:	Multiple
Whiteboard:	backport 3.2
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know

Description Yann Dirson 2020-10-19 08:26:03 UTC

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

Comment 1 Richard Purdie 2020-10-19 14:05:44 UTC

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...

Comment 2 Yann Dirson 2020-10-20 02:19:11 UTC

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 ?

Comment 3 Randy MacLeod 2023-07-26 21:22:05 UTC

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.

Comment 4 Trevor Gamblin 2023-09-14 16:37:06 UTC

Moved to M4.

Comment 5 Randy MacLeod 2023-10-30 15:29:08 UTC

Bulk move to 5.0 M1. -- Randy

Comment 6 Randy MacLeod 2023-12-21 23:28:24 UTC

Bulk move of 52 5.0-M1 bugs to M2.

Comment 7 Randy MacLeod 2024-01-25 14:28:48 UTC

Bulk move of bugs owned by "unassigned" from 5.0-M2 to 5.0-M3.

Comment 8 Randy MacLeod 2024-02-22 19:53:25 UTC

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.

Comment 9 Randy MacLeod 2026-03-18 21:51:08 UTC

The extensible SDK subsystem still needs work but few users seem to notice.
Move to 6.99 as a holding milestone.