Bug 7135 - ASSUME_PROVIDED_remove = "git-native" in local.conf does not work as expected
Summary: ASSUME_PROVIDED_remove = "git-native" in local.conf does not work as expected
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.8 M3
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-01-13 17:56 UTC by Phlip Balister
Modified: 2015-01-23 14:27 UTC (History)
2 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 Phlip Balister 2015-01-13 17:56:29 UTC 
For customer reasons, I need git in the native sysroot (I'm not saying this is a good idea).

So I put:

ASSUME_PROVIDED_remove = "git-native"

in local.conf. The I run:

[balister@thuvia build]$ bitbake -e gnuradio-dev-image | grep ^ASSUME_PROVIDED
ASSUME_PROVIDED="bzip2-native chrpath-native grep-native diffstat-native patch-native perl-native-runtime python-native-runtime tar-native virtual/libintl-native texinfo-native bash-native"

Note git-native has been removed as expected. Now I try:

bitbake git-native

but bitbake reports:

WARNING: Explicit target "git-native" is in ASSUME_PROVIDED, ignoring

I know I can edit the oe-core file to change this, but I am trying to work with upstream oe-core and not carry local hacks.
Comment 1 Richard Purdie 2015-01-21 16:08:39 UTC 
Patch out on the bitbake list.