aboutsummaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-support/p910nd
Commit message (Collapse)AuthorAgeFilesLines
* p910nd: Fix the lock directory useOtavio Salvador2013-04-222-2/+33
| | | | | | | | | The original code uses a subdir inside of /var/lock which is hard for us to manage as it may be running in tmpfs; we did change it for avoid the subdir so it just works. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* recipes: Unify indentationMartin Jansa2013-04-151-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | * 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>
* p910nd: drop unused init scriptOtavio Salvador2011-05-102-41/+2
| | | | Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
* p910nd: add version 0.95Otavio Salvador2011-05-102-0/+60
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>