Just out of my curiosity: How are PREFERRED_VERSION_pkg supposed to work when I prefer pkg with autoreved revision. bbfile will be named like pkg_git.bb inside will be PV="1.0.0+gitr${SRCPV}" and DEFA

What about this small patch in attachment? Is there better character for wildchar ('*')? For this type of PVs is wildchar usefull only in the end of PREFERRED_VERSION_pkg, would someone need it somewh

--- lib/bb/providers.py | 13 ++++++++++++- 1 files changed, 12 insertions(+), 1 deletions(-) diff --git a/lib/bb/providers.py b/lib/bb/providers.py index 8970fb3..feaee52 100644 --- a/lib/bb/providers

As I'm not python programmer, I should at least test it better :/ sorry for that noise. true->True, false->False better version in attachment

I had problem when using _git or _svn versions with AUTOREV. When there is SRCREV or SRCPV in PV of that bb file you would like to use then you need to update PREFERRED_VERSION_pkg with every new comm

I wrote a bit more about my problem here: http://article.gmane.org/gmane.comp.handhelds.openembedded/25986 Simply: If I want to prefer bbfile with PV=1.0+gitr${SRCPV} then PV will change with every co

Ok, but then you can say, that the same problem is when there is two or more packages with PV = "1.0". You can have as many git-based bb files as long as they have different PV prefix like 1.0+git% an

Move update-alternatives logic to findutils-alternatives.inc which is not included in -native packages. Patch mkinstalldirs.patch is needed also for findutils-native_4.2.29. Remove version 4.4 as ther

--- .../include/preferred-xorg-versions-live.inc | 637 ++++++++++++++++++++ conf/distro/include/sane-srcrevs.inc | 3 +- .../bump.preferred-xorg-versions-live.sh | 68 +++ recipes/dri/libdrm-glamo_git.b

Sure, but I was probably wrong to create new provider for drm.. seems like not needed for oe.dev branch. I'll create libdrm_git.bb and alternate SRC_URI for om-gta02 machine with glamo. What would you

--- conf/distro/include/sane-srcrevs.inc | 1 + recipes/dri/libdrm-glamo_git.bb | 17 ----------------- recipes/dri/libdrm_git.bb | 19 +++++++++++++++++++ 4 files changed, 30 insertions(+), 19 deletions

--- .../xorg-xserver/xserver-xorg-1.7.0/dolt-fix.patch | 21 ++++++++++++++++++++ 1 files changed, 21 insertions(+), 0 deletions(-) create mode 100644 recipes/xorg-xserver/xserver-xorg-1.7.0/dolt-fix.p

--- conf/checksums.ini | 28 ++++++++++++++++++++++++++++ 1 files changed, 28 insertions(+), 0 deletions(-) diff --git a/conf/checksums.ini b/conf/checksums.ini index 097d63d..679e282 100644 --- a/conf

--- conf/distro/include/preferred-shr-versions.inc | 2 -- conf/distro/include/shr-om-gta02-kms.conf | 3 --- conf/distro/include/shr-om-gta02.conf | 4 ++-- conf/machine/om-gta02.conf | 1 - 4 files chan

--- .../glibc-2.9/glibc-2.9-enable-binutils-2.2.patch | 35 ++++++++++++++++++++ recipes/glibc/glibc_2.9.bb | 1 + 2 files changed, 36 insertions(+), 0 deletions(-) create mode 100644 recipes/glibc/glib

Hi all OE developers, I am politely asking if would be possible to allow me OE commit access. I already promised to commit this stuff: 1) xorg-7.5 2) scripts for easier updating of checksums.ini 3) SR

From: Martin Jansa <Martin.Jansa@...> * Updated patch to make SYSCALL_ERROR_HANDLER interworking safe. * Phil Blundell found and fixed another issue in eglibc armv4t builds. Signed-off-by: Marti

http://cgit.openembedded.net/cgit.cgi/openembedded/commit/?h=shr/merge&id=b7c9855c7ece03a0876c0d50922f908b65c5f095 should be also cherry-picked to replace another __ARM_ARCH_V4T__ with __ARM_ARCH_4T__

Hi, From what I checked now in linux.inc, then you're right that do_menuconfig is called just after do_patch, which seems wrong, because in do_configure_prepend it prepares few lines to .config (like

* Holger Hans Peter Freyther <zecke@...> did for the OM git tree that was never merged back into OE. * Taken from xora/angstrom-srcpv branch where it rot for long enough --- conf/bitbake.conf