Bug 407 - Usability: How to find specific variables and settings?
Summary: Usability: How to find specific variables and settings?
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 0.9
Hardware: x86 Multiple
: Low enhancement
Target Milestone: Future
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-10-07 14:45 UTC by Mark Hatle
Modified: 2014-07-25 17:19 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Hatle 2010-10-07 14:45:03 UTC
There is a usability issue where it can be difficult to understand what settings are available and what the potential system/distro defaults are.

Normally, I'd look at the individual package recipes, and potentially the conf/local.conf to try to figure out the system settings.  It's not clear on the surface that there are additional configuration settings elsewhere that should NOT be modified by the user, but should be overridden by adding them to conf/local.conf.

We need to find a better way to expose this so users can "help themselves" when they don't like the defaults, or perhaps want to change some piece of system behavior.
Comment 1 Richard Purdie 2010-10-07 14:46:37 UTC
The solution is probably to slim down the offerings in local.conf and make it clear the defaults come from the distro configuration (i.e. poky.conf).
Comment 2 Richard Purdie 2014-07-25 17:19:00 UTC
Several things have changed in the past 4 years:

* Better documentation of variables in the manual
* local.conf.sample.extended now exists
* bitbake -e shows variable history

So I think we're good to close this and if there are specific problems, open specific bugs for those.