* This change is only aesthetic (unlike indentation in Python
tasks).
* Some recipes were using tabs.
* Some were using 8 spaces.
* Some were using mix or different number of spaces.
* Make them consistently use 4 spaces everywhere.
* Yocto styleguide advises to use tabs (but the only reason to keep
tabs is the need to update a lot of recipes). Lately this advice
was also merged into the styleguide on the OE wiki.
* Using 4 spaces in both types of tasks is better because it's less
error prone when someone is not sure if e.g.
do_generate_toolchain_file() is Python or shell task and also allows
to highlight every tab used in .bb, .inc, .bbappend, .bbclass as
potentially bad (shouldn't be used for indenting of multiline
variable assignments and cannot be used for Python tasks).
* Don't indent closing quote on multiline variables
we're quite inconsistent wheater it's first character on line
under opening quote or under first non-whitespace character in
previous line.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Acked-by: Koen Kooi <koen@dominion.thruhere.net>
* chrpath-native was added to ASSUME_PROVIDED
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-October/030744.html
* it would be better to not use chrpath at all, but build.txt says:
If you do not have chrpath available, GPSD binaries will be built
statically.
...
When you are cross-compiling, you'll need chrpath at version 0.14 or
later for cross-architecture support. If it's not yet packaged for
your environment, see http://alioth.debian.org/projects/chrpath/
and I prefer to stick to upstream
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* it could be something machine specific (config + hoooks) and we don't want gpsd sstate checksum depending on MACHINE var
* gpsd-machine-conf itself is using u-a to select right config
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
