Files enlightenment-0.17.2.1/ChangeLog and enlightenment-0.17.2.1-new/ChangeLog differ
Files enlightenment-0.17.2.1/NEWS and enlightenment-0.17.2.1-new/NEWS differ
Files enlightenment-0.17.2.1/po/ca.gmo and enlightenment-0.17.2.1-new/po/ca.gmo differ
Files enlightenment-0.17.2.1/po/ca.po and enlightenment-0.17.2.1-new/po/ca.po differ
Files enlightenment-0.17.2.1/po/eo.gmo and enlightenment-0.17.2.1-new/po/eo.gmo differ
Files enlightenment-0.17.2.1/po/eo.po and enlightenment-0.17.2.1-new/po/eo.po differ
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* 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>
Files old/evas-1.7.6.1/ChangeLog and new/evas-1.7.6.1/ChangeLog differ
Files old/evas-1.7.6.1/NEWS and new/evas-1.7.6.1/NEWS differ
Files old/evas-1.7.6.1/src/lib/engines/common/evas_font_ot.c and new/evas-1.7.6.1/src/lib/engines/common/evas_font_ot.c differ
Files old/evas-1.7.6.1/src/tests/evas_test_textblock.c and new/evas-1.7.6.1/src/tests/evas_test_textblock.c differ
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
| -- checking for module 'edbus>=1.1.0'
| -- package 'edbus>=1.1.0' not found
| -- checking for module 'eukit>=1.1.0'
| -- package 'eukit>=1.1.0' not found
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* edbus2 was merged in efl tree and moved to IN-EFL in r81826
there is important fix also in IN-EFL/edbus2
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* meta-openembedded/meta-oe/recipes-devtools/lemon/lemon_3.5.4.bb provides almost the same lemon
but lemon.c in azy sources is a bit modified (and completely reformatted :/)
* rename it to resolve:
WARNING: The recipe azy-native is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/OE/jansa-test/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/bin/lemon
Matched in manifest-x86_64-lemon-native
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* probably because of
http://git.openembedded.org/bitbake/commit/?id=9fc98f96f0e0320beda0ce9546275a99336732c1
it now failed with
/OE/jansa-test/shr-core/tmp-eglibc/work/x86_64-linux/azy-native/2_1.0.0+svnr80969-r0/temp/run.do_configure.30731: line 88: efl_do_configure: command not found
ERROR: Function failed: do_configure (see /OE/jansa-test/shr-core/tmp-eglibc/work/x86_64-linux/azy-native/2_1.0.0+svnr80969-r0/temp/log.do_configure.30731 for further information)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* we don't have vlc in DEPENDS, but when it happens to be built before
emotion, it causes undeterministic builds and unpackaged files
emotion-1.7.3: emotion: Files/directories were installed but not
shipped
/usr/lib/emotion/utils/em_generic_vlc
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* called from xkb map E17 module
Jan 02 02:58:42 gjama xinit[418]: SET XKB RUN: setxkbmap -model 'default'
Jan 02 02:58:42 gjama xinit[418]: SET XKB RUN: setxkbmap -model 'default'
Jan 02 02:58:43 gjama xinit[418]: /bin/sh: setxkbmap: command not found
Jan 02 02:58:43 gjama xinit[418]: /bin/sh: setxkbmap: command not found
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Martin Jansa