Bug 13449 - Functionality of Unpack parameter 'basepath' broken
Summary: Functionality of Unpack parameter 'basepath' broken
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 2.7.1
Hardware: x86 Multiple
: Medium normal
Target Milestone: 3.4
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2019-07-23 08:29 UTC by Volker
Modified: 2021-04-20 13:10 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Volker 2019-07-23 08:29:22 UTC 
Doc https://www.yoctoproject.org/docs/2.7.1/bitbake-user-manual/bitbake-user-manual.html#bb-the-unpack
describes a parameter 'basepath'
"...to strip the specified directories from the source path when unpacking..."
--> This functionality seems to be broken.

Checking latest sources I found that this commit
"bitbake: fetch2: fixes copying of file://dir; subdir=foo, bug 6128 and bug 6129"
of Feb. 2016 seems to have removed handling of the respective parameter from source file bitbake/lib/bb/fetch2/__init__.py

A grep in latest sources for 'parm.get(' shows hits for the other options unpack, dos, subdir but not for basepath.

(This open question at stackoverflow seems to address the same topic, while referring to v1.6:
https://stackoverflow.com/questions/50451961/stripping-base-path-off-the-unpacked-source-tree-with-bitbake-src-uri-file-fe?rq=1)
Comment 1 Richard Purdie 2021-04-19 11:24:05 UTC 
Patch sent to update the docs.