Setting PRSERV_HOST and PRSERV_PORT would trigger the poky to use remote
PR network service. Leaving them unset allow the user to build image
without the PR network service
Signed-off-by: Lianhao Lu
---
meta-yocto/conf/local.conf.sample |5 +
1 files changed, 5 insertions(+), 0 deletions
Signed-off-by: Lianhao Lu
---
meta/recipes-graphics/xcb/libpthread-stubs_0.3.bb |2 +-
meta/recipes-graphics/xcb/xcb-proto.inc |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-graphics/xcb/libpthread-stubs_0.3.bb
b/meta/recipes-graphics/xcb/lib
1. Added package_get_auto_pr to PACKAGEFUNCS to get the auto
incremented value(PRAUTO) from remote PR service.
2. use PKGV/PKGR for pkgdata which will be used by package_write_xxx.
3. Added supporting functions in prserv.bbclass.
Signed-off-by: Lianhao Lu
---
meta/classes/package.bbclass | 5
Signed-off-by: Lianhao Lu
---
.../xorg-util/util-macros_1.13.0.bb|2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-graphics/xorg-util/util-macros_1.13.0.bb
b/meta/recipes-graphics/xorg-util/util-macros_1.13.0.bb
index a708ed0..a6f5402 100644
-
Signed-off-by: Lianhao Lu
---
.../linux-libc-headers/linux-libc-headers.inc |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc
b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc
index 8c5dc76..
Removed the unused variable EXTENDPV and EXTENDPEVER. User should use
EXTENDPKGV instead for package feed generation.
Signed-off-by: Lianhao Lu
---
meta/conf/bitbake.conf |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
ind
Use PKGE/PKGV/PKGR to build various package feed in tasks of pacakge_write_xxx.
Signed-off-by: Lianhao Lu
---
meta/classes/package_deb.bbclass |8
meta/classes/package_ipk.bbclass |8
meta/classes/package_rpm.bbclass | 14 +++---
meta/classes/package_tar.bbcla
Signed-off-by: Lianhao Lu
---
.../xorg-proto/xorg-proto-common.inc |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-graphics/xorg-proto/xorg-proto-common.inc
b/meta/recipes-graphics/xorg-proto/xorg-proto-common.inc
index ab1af28..765e30a 100644
Added the initial implementation of the server side PR service.
Signed-off-by: Lianhao Lu
---
bitbake/bin/bitbake-prserv | 53 +++
bitbake/lib/prserv/__init__.py | 11 ++
bitbake/lib/prserv/db.py | 100
bitbake/lib/prserv/serv.py | 198 +++
Signed-off-by: Lianhao Lu
---
meta/recipes-core/udev/udev-new.inc |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-core/udev/udev-new.inc
b/meta/recipes-core/udev/udev-new.inc
index d1abf39..1b94f1b 100644
--- a/meta/recipes-core/udev/udev-new.inc
+++ b/meta
1. change BB_SIGNATURE_HANDLER from basic to basichash.
2. Added following variables for PR service:
USE_PR_SERV: flag of whether to use the network PR service
PRAUTOINX: search index for the network PR service
PKGE/PKGV/PKGR: epoch, version and revision used in package feed.
EXTENDPKGV: full pack
This is a modification of the original patch to enable network based PR
service.
The main difference between this series of patch to the original one is that
this one uses the PKGR/PKGV during the package feed creation, and use
EXTENDPKGV
instead of EXTENDPV for package dependencies.
It also
On 05/26/2011 01:41 PM, nitin.a.kam...@intel.com wrote:
> From: Nitin A Kamble
>
> Fixes this bug [YOCTO #1105]
>
> Working around this issue withg gcc 4.6.0 for beagleboard machine (armv7)
>
> ccache arm-poky-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon
> -mfloat-abi=softfp -fn
From: Khem Raj
While building for beagleboard with -j4 I ended up failures in
generating and checking xml files. This is a backport from upstream that
fixes the issue.
Signed-off-by: Khem Raj
---
.../files/fix-parallel-build-backport.patch| 26
.../shared-mime-in
This will configure uclibc to be compiled in thumb/thumb2 mode
Signed-off-by: Khem Raj
---
meta/recipes-core/uclibc/uclibc.inc |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/meta/recipes-core/uclibc/uclibc.inc
b/meta/recipes-core/uclibc/uclibc.inc
index e7d8846..c1bc42
Signed-off-by: Khem Raj
---
.../uclibc-git/append_UCLIBC_EXTRA_CFLAGS.patch| 33
.../uclibc-git/compile-arm-fork-with-O2.patch | 21
meta/recipes-core/uclibc/uclibc_git.bb |4 ++-
3 files changed, 57 insertions(+), 1 deletions(-)
cre
slugos uses uclibc in thumb mode. These patches fix the build of uclibc in
thumb mode
and additionally fixes shared-mime-info which failed to build with -j4
The following changes since commit 31b3d1f9aa6fa1640874f7da9cce37f4aa13eab1:
uclibc_git.bb: Fix compilation on arm when using thumb instr
On Fri, May 27, 2011 at 12:13:35AM +0100, Richard Purdie wrote:
> On Fri, 2011-05-27 at 00:08 +0200, Martin Jansa wrote:
> > Good evening,
> >
> > sorry for long and pesimistic e-mail, but I hope that someone will point
> > me to something I'm doing completely wrong.
> >
> > First I was surprised
On Thu, May 26, 2011 at 20:07, Darren Hart wrote:
> My current thinking on this is that for meta-yocto we want to have a
> reasonably functional self-contained example BSP for ARM. Beagleboard
> was the board selected for that. meta-yocto should be able to build the
> core-image-* images and have
On 05/26/2011 09:29 PM, Saul Wold wrote:
> On 05/26/2011 09:07 PM, Darren Hart wrote:
>>
>>
>> On 05/26/2011 02:14 PM, Paul Eggleton wrote:
>>> On Thursday 26 May 2011 22:03:02 Darren Hart wrote:
Yeah, this wasn't clear to me either. And my question in 2/2 still
stands - what is the goa
On 05/26/2011 09:07 PM, Darren Hart wrote:
On 05/26/2011 02:14 PM, Paul Eggleton wrote:
On Thursday 26 May 2011 22:03:02 Darren Hart wrote:
Yeah, this wasn't clear to me either. And my question in 2/2 still
stands - what is the goal of the overhead factor?
I think the thinking was that the
On 05/26/2011 02:14 PM, Paul Eggleton wrote:
> On Thursday 26 May 2011 22:03:02 Darren Hart wrote:
>> Yeah, this wasn't clear to me either. And my question in 2/2 still
>> stands - what is the goal of the overhead factor?
>
> I think the thinking was that the more software you have installed to
On 05/26/2011 04:24 PM, Richard Purdie wrote:
> On Thu, 2011-05-26 at 14:12 -0700, Darren Hart wrote:
>> Note: I used bb.note() instead of bb.debug() to ensure the message at least
>> makes it to the console. From what I could gather, bb.debug() doesn't
>> go anywhere during recipe pa
On 05/26/2011 04:46 PM, Richard Purdie wrote:
> On Wed, 2011-05-25 at 16:05 -0700, Darren Hart wrote:
>> Fixes [YOCTO 1102]
>>
>> Path variables are typically : delimited. White space is allowed in paths, so
>> is not a good choice for separating paths. Currently utils.bbclass performs
>> the
>>
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Khem Raj
> Sent: Thursday, May 26, 2011 5:37 PM
> To: Patches and discussions about the oe-core layer
> Subject: Re: [OE-core] [bugfix 1
On Thu, May 26, 2011 at 4:33 PM, Richard Purdie
wrote:
> On Thu, 2011-05-26 at 13:41 -0700, nitin.a.kam...@intel.com wrote:
>
>> ---
>> meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb | 3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/meta/recipes-graphics/mesa/mesa
On Wed, 2011-05-25 at 16:05 -0700, Darren Hart wrote:
> Fixes [YOCTO 1102]
>
> Path variables are typically : delimited. White space is allowed in paths, so
> is not a good choice for separating paths. Currently utils.bbclass performs
> the
> following:
>
> extrapaths = (bb.data.getVar("FILE
On 05/26/2011 02:31 AM, Martin Jansa wrote:
* this makes fix for [YOCTO #1074] in bitbake
139b8a625818225c358a1b8363518d7ed6913188
much more usefull for people using rm_work
Signed-off-by: Martin Jansa
---
meta/classes/rm_work.bbclass |4
1 files changed, 4 insertions(+), 0 delet
On Thu, 2011-05-26 at 16:07 -0700, Saul Wold wrote:
> Darren Hart (1):
> utils.bbclass: make FILESEXTRAPATHS colon delimited
Feedback to patch sent, can be simplified (I think).
> Koen Kooi (2):
> dbus: clean up dbus-x11 packaging
> x11-common: fix dbus-launch RDEPENDS
Merged
> Martin Jan
On Thu, 2011-05-26 at 17:18 +0200, Koen Kooi wrote:
> Op 24 mei 2011, om 16:04 heeft Koen Kooi het volgende geschreven:
>
> > In the current situation TARGET_ARCH will override MACHINE, which is
> > counter intuitive since the machine is more specific than the arch.
> >
> > The order is now pn-$
On Thu, May 26, 2011 at 4:24 PM, Richard Purdie
wrote:
> On Thu, 2011-05-26 at 14:12 -0700, Darren Hart wrote:
>> Note: I used bb.note() instead of bb.debug() to ensure the message at least
>> makes it to the console. From what I could gather, bb.debug() doesn't
>> go anywhere during r
On Thu, 2011-05-26 at 13:41 -0700, nitin.a.kam...@intel.com wrote:
> ---
> meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb |3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb
> b/meta/recipes-graphics/mesa/mesa-xlib_7.10.
On Thu, 2011-05-26 at 21:45 +0200, Koen Kooi wrote:
> Martin Jansa spotted some differences with OE dev, which this commit fixes:
>
> * dbus-launch is mentioned twice in FILES
> * dbus-x11 should drag in dbus-1
>
> Signed-off-by: Koen Kooi
> ---
>
> Try 3, now with git --amend working properl
On Thu, 2011-05-26 at 21:42 +0200, Koen Kooi wrote:
> /usr/bin/dbus-launch is in the dbus-x11 packages, the dbus-launch package
> doesn't exist
>
> Signed-off-by: Koen Kooi
> ---
> meta/recipes-graphics/x11-common/x11-common_0.1.bb |4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
On Thu, 2011-05-26 at 14:12 -0700, Darren Hart wrote:
> Note: I used bb.note() instead of bb.debug() to ensure the message at least
> makes it to the console. From what I could gather, bb.debug() doesn't
> go anywhere during recipe parsing.
Why?
We exclude about 30 different recipes w
On Fri, 2011-05-27 at 00:08 +0200, Martin Jansa wrote:
> Good evening,
>
> sorry for long and pesimistic e-mail, but I hope that someone will point
> me to something I'm doing completely wrong.
>
> First I was surprised to see how many recipes were rebuilt after this
> change:
> http://git.openem
From: Koen Kooi
/usr/bin/dbus-launch is in the dbus-x11 packages, the dbus-launch package
doesn't exist
Signed-off-by: Koen Kooi
---
meta/recipes-graphics/x11-common/x11-common_0.1.bb |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-graphics/x11-common/
Signed-off-by: Saul Wold
---
meta/conf/bitbake.conf | 11 ++-
1 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 35fd6f8..d307385 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -347,13 +347,14 @@ IMAG
From: Koen Kooi
Martin Jansa spotted some differences with OE dev, which this commit fixes:
* dbus-launch is mentioned twice in FILES
* dbus-x11 should drag in dbus-1
Signed-off-by: Koen Kooi
---
meta/recipes-core/dbus/dbus.inc |2 +-
meta/recipes-core/dbus/dbus_1.4.1.bb |2 +-
From: Martin Jansa
* this makes fix for [YOCTO #1074] in bitbake
139b8a625818225c358a1b8363518d7ed6913188
much more usefull for people using rm_work
Signed-off-by: Martin Jansa
---
meta/classes/rm_work.bbclass |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/meta/
Setup INC_PR for PR bumps
Signed-off-by: Saul Wold
---
meta/recipes-support/gnutls/gnutls.inc |6 --
meta/recipes-support/gnutls/gnutls_2.10.4.bb |2 +-
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-support/gnutls/gnutls.inc
b/meta/recipes-support
From: Nitin A Kamble
Fixes this bug [YOCTO #1105]
Working around this issue withg gcc 4.6.0 for beagleboard machine (armv7)
ccache arm-poky-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon
-mfloat-abi=softfp -fno-tree-vectorize
--sysroot=/build_disk/poky_build/build0/tmp/sysroots/be
There a number of changes here for M1.
Nitin's change is included since it was queued already, bounce as needed
Sau!
The following changes since commit 9281ac4c98d4287a5492f13f94e1bd0eea4791c6:
dbus 1.4.1: enable systemd support, but package systemd files seperately
(2011-05-26 11:02:30 +01
From: Darren Hart
Fixes [YOCTO 1102]
Path variables are typically : delimited. White space is allowed in paths, so
is not a good choice for separating paths. Currently utils.bbclass performs the
following:
extrapaths = (bb.data.getVar("FILESEXTRAPATHS", d, True) or "").split()
This splits
This was just the wrong update to go to, it was not fully vetted
and contains yum requirements which is not a direction we are moving
in.
This reverts commit 7576eba58cdfebf0606623c25ae969ef52774099.
Signed-off-by: Saul Wold
---
.../createrepo/createrepo/fix-native-install.patch | 88
From: Phil Blundell
This is basically a backport of the current state of the art from the
openembedded master repo. In particular this fixes an installation
error on micro:
| + cp -dPr
/home/pb/oe/build-meta/tmp-eglibc/work/i586-oe-linux/busybox-1.18.4-r1.2/image/bin
/home/pb/oe/build-meta/t
Good evening,
sorry for long and pesimistic e-mail, but I hope that someone will point
me to something I'm doing completely wrong.
First I was surprised to see how many recipes were rebuilt after this
change:
http://git.openembedded.net/cgit.cgi/openembedded-core/commit/?id=aebb9d6599aac683456adf
On Thu, 2011-05-26 at 14:15 -0700, Saul Wold wrote:
> On 05/26/2011 02:13 PM, Joshua Lock wrote:
> > On Thu, 2011-05-26 at 14:03 -0700, Darren Hart wrote:
> >>
> >> On 05/26/2011 02:01 PM, Joshua Lock wrote:
> >>> On Thu, 2011-05-26 at 13:55 -0700, Darren Hart wrote:
>
> On 05/26/2011 12:
On Wed, 2011-05-25 at 16:30 -0700, Elizabeth Flanagan wrote:
> This pull request is a consolidated pull of some changes to the
> license.bbclass
> license parsing, some cleanup of existing licenses, and some additions to/
> modifications of various licenses kept in meta/files/common-licenses.
>
>
On Wed, 2011-05-25 at 16:30 -0700, Elizabeth Flanagan wrote:
> This is a first pass at sane license parsing, using python
> abstract syntax trees.
>
> A few notes on this since ast is not generally used. I massage
> the LICENSE field to be more pythonesque and then create an ast.
>
> I then dump
> > +# nullify -O2
>
> Can we specify why this is being done here in the recipe? We do this in
> other areas, something like:
>
> # GCC 4.6.0 hits an internal compiler error using -O2
> # use -O to workaround.
Darren,
Good Point, I will update the comment in the tree.
>
> This make it obviou
On 05/26/2011 02:13 PM, Joshua Lock wrote:
On Thu, 2011-05-26 at 14:03 -0700, Darren Hart wrote:
On 05/26/2011 02:01 PM, Joshua Lock wrote:
On Thu, 2011-05-26 at 13:55 -0700, Darren Hart wrote:
On 05/26/2011 12:54 PM, Joshua Lock wrote:
On Thu, 2011-05-26 at 11:28 -0700, Saul Wold wrote:
O
On Thursday 26 May 2011 22:03:02 Darren Hart wrote:
> Yeah, this wasn't clear to me either. And my question in 2/2 still
> stands - what is the goal of the overhead factor?
I think the thinking was that the more software you have installed to begin
with the more user data you're likely to need to
oe-core does not define any machines, so it does not make sense to
add machine specific information in the oe-core u-boot recipe and
infrastructure. Also note that COMPATIBLE_MACHINES is not easily extended due to
its regex syntax: "(machine_a|machine_b)", making it difficult to extend the
u-boot r
Tested via build/install/boot of core-image-minimal with the meta-yocto
beagleboard machine config.
V2: Fixup the message printed if u-boot is skipped so it:
1) appears on the console
2) prints the name of the including u-boot recipe for reference
(instead of a hard coded name)
The
In order to facilitate reuse of the oe-core u-boot recipe, there needs to be
some assurance that the oe-core version won't change without a clear indicator
to people extending it.
By renaming the recipe to include its version string instead of "git", BSP
layers can extend a specific base version o
On Thu, 2011-05-26 at 14:03 -0700, Darren Hart wrote:
>
> On 05/26/2011 02:01 PM, Joshua Lock wrote:
> > On Thu, 2011-05-26 at 13:55 -0700, Darren Hart wrote:
> >>
> >> On 05/26/2011 12:54 PM, Joshua Lock wrote:
> >>> On Thu, 2011-05-26 at 11:28 -0700, Saul Wold wrote:
> On 05/26/2011 11:04 A
On Thu, 2011-05-26 at 13:55 -0700, Darren Hart wrote:
>
> On 05/26/2011 12:54 PM, Joshua Lock wrote:
> > On Thu, 2011-05-26 at 11:28 -0700, Saul Wold wrote:
> >> On 05/26/2011 11:04 AM, Joshua Lock wrote:
> >>> On Mon, 2011-05-23 at 23:38 -0700, Saul Wold wrote:
> This basic cleanup removes t
Signed-off-by: Martin Jansa
---
.../console-tools/console-tools_0.3.2.bb |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-core/console-tools/console-tools_0.3.2.bb
b/meta/recipes-core/console-tools/console-tools_0.3.2.bb
index c7bee61..c740119 1
On 05/26/2011 02:01 PM, Joshua Lock wrote:
> On Thu, 2011-05-26 at 13:55 -0700, Darren Hart wrote:
>>
>> On 05/26/2011 12:54 PM, Joshua Lock wrote:
>>> On Thu, 2011-05-26 at 11:28 -0700, Saul Wold wrote:
On 05/26/2011 11:04 AM, Joshua Lock wrote:
> On Mon, 2011-05-23 at 23:38 -0700, Saul
On 05/26/2011 11:22 AM, Saul Wold wrote:
> On 05/26/2011 11:04 AM, Joshua Lock wrote:
>> On Mon, 2011-05-23 at 23:38 -0700, Saul Wold wrote:
>>> [YOCTO #886]
>>>
>>> This address 2 needs after the IMAGE_ROOTFS_SIZE is cleaned up, by
>>> removing some of the _ext2/3 overrides it allows for a clean
On 05/26/2011 12:54 PM, Joshua Lock wrote:
> On Thu, 2011-05-26 at 11:28 -0700, Saul Wold wrote:
>> On 05/26/2011 11:04 AM, Joshua Lock wrote:
>>> On Mon, 2011-05-23 at 23:38 -0700, Saul Wold wrote:
This basic cleanup removes the _ext2/3 overrides from places they
no longer belong since
From: Nitin A Kamble
The following changes since commit 5168b140183c569409d35b19d8a80265ef8d0a78:
dbus 1.4.1: enable systemd support, but package systemd files seperately
(2011-05-26 16:52:00 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib nitin/bugfixes
From: Nitin A Kamble
Fixes this bug [YOCTO #1105]
Working around this issue withg gcc 4.6.0 for beagleboard machine (armv7)
ccache arm-poky-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon
-mfloat-abi=softfp -fno-tree-vectorize
--sysroot=/build_disk/poky_build/build0/tmp/sysroots/be
On Thu, 2011-05-26 at 11:28 -0700, Saul Wold wrote:
> On 05/26/2011 11:04 AM, Joshua Lock wrote:
> > On Mon, 2011-05-23 at 23:38 -0700, Saul Wold wrote:
> >> This basic cleanup removes the _ext2/3 overrides from places they
> >> no longer belong since they did not allow further overrides. In doing
Martin Jansa spotted some differences with OE dev, which this commit fixes:
* dbus-launch is mentioned twice in FILES
* dbus-x11 should drag in dbus-1
Signed-off-by: Koen Kooi
---
Try 3, now with git --amend working properly. With a special thanks to Martin
who tells me about these stupid ty
/usr/bin/dbus-launch is in the dbus-x11 packages, the dbus-launch package
doesn't exist
Signed-off-by: Koen Kooi
---
meta/recipes-graphics/x11-common/x11-common_0.1.bb |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-graphics/x11-common/x11-common_0.1.bb
Martin Jansa spotted some differences with OE dev, which this commit fixes:
* dbus-launch is mentioned twice in FILES
* dbus-x11 should drag in dbus-1
Signed-off-by: Koen Kooi
---
meta/recipes-core/dbus/dbus.inc |2 +-
meta/recipes-core/dbus/dbus_1.4.1.bb |2 +-
2 files changed,
Martin Jansa spotted some differences with OE dev, which this commit fixes:
* dbus-launch is mentioned twice in FILES
* dbus-x11 should drag in dbus-1
Signed-off-by: Koen Kooi
---
meta/recipes-core/dbus/dbus.inc |2 +-
meta/recipes-core/dbus/dbus_1.4.1.bb |2 +-
2 files changed,
On 05/26/2011 11:04 AM, Joshua Lock wrote:
On Mon, 2011-05-23 at 23:38 -0700, Saul Wold wrote:
This basic cleanup removes the _ext2/3 overrides from places they
no longer belong since they did not allow further overrides. In doing
this the core-image-minimal* recipes can now set a reasonably sma
On 05/26/2011 11:04 AM, Joshua Lock wrote:
On Mon, 2011-05-23 at 23:38 -0700, Saul Wold wrote:
[YOCTO #886]
This address 2 needs after the IMAGE_ROOTFS_SIZE is cleaned up, by
removing some of the _ext2/3 overrides it allows for a cleaner override
using IMAGE_ROOTFS_SIZE to create a large rootfs
Hi Jason,
On 05/25/2011 04:31 PM, Jason Kridner wrote:
> This thread got pretty long pretty fast, but I am imagining there is some
> place still here for me to chime in and build my own understanding of what
> we are doing...
Of course, thanks for the input...
>
> On Wed, May 25, 2011 at 5:51 P
On Mon, 2011-05-23 at 23:38 -0700, Saul Wold wrote:
> [YOCTO #886]
>
> This address 2 needs after the IMAGE_ROOTFS_SIZE is cleaned up, by
> removing some of the _ext2/3 overrides it allows for a cleaner override
> using IMAGE_ROOTFS_SIZE to create a large rootfs, or by setting the
> IMAGE_ROOTFS_E
On Mon, 2011-05-23 at 23:38 -0700, Saul Wold wrote:
> This basic cleanup removes the _ext2/3 overrides from places they
> no longer belong since they did not allow further overrides. In doing
> this the core-image-minimal* recipes can now set a reasonably small
> rootfs so that it's a realistic siz
On 05/26/2011 09:18 AM, Phil Blundell wrote:
> On Thu, 2011-05-26 at 15:37 +0100, Richard Purdie wrote:
>> u-boot in OE-Core would need something like COMPATIBLE_MACHINE = ""
>> which makes this harder.
>
> Yes, true. I don't think that's a major problem, though, you just need
> a regex that wo
On Thu, 2011-05-26 at 15:37 +0100, Richard Purdie wrote:
> u-boot in OE-Core would need something like COMPATIBLE_MACHINE = ""
> which makes this harder.
Yes, true. I don't think that's a major problem, though, you just need
a regex that won't match anything. Something like:
COMPATIBLE_MACHINE
Op 24 mei 2011, om 16:04 heeft Koen Kooi het volgende geschreven:
> In the current situation TARGET_ARCH will override MACHINE, which is counter
> intuitive since the machine is more specific than the arch.
>
> The order is now pn-$PN} -> arch -> machine -> distro as the machine is a set
> of
On Thu, 2011-05-26 at 11:50 +0100, Phil Blundell wrote:
> On Wed, 2011-05-25 at 22:02 -0700, Darren Hart wrote:
> > COMPATIBLE_MACHINES is not easily extended due to
> > its regex syntax: "(machine_a|machine_b)", making it difficult to extend the
> > u-boot recipe in bbappend files without resortin
On Thu, 2011-05-26 at 14:07 +0100, Phil Blundell wrote:
> On Thu, 2011-05-26 at 21:02 +0800, Lu, Lianhao wrote:
> > Maybe all the recipes are using the PKGV default value (?= ${PV}, so
> > this just happens to make EXTENDPKGV equal to EXTENDPV.
>
> Yes, could be. The most common situation where
On Thu, May 26, 2011 at 6:50 AM, Darren Hart wrote:
>>> -UBOOT_MACHINE ?= "${MACHINE}_config"
>>> +python () {
>>> + if not bb.data.getVar('UBOOT_MACHINE', d, 1):
>>> + bb.debug("To build %s, see u-boot_git.bb for instructions on \
>>
>> If this file was renamed, don't you also want to u
On 05/25/2011 11:12 PM, Anders Darander wrote:
> On Wed, May 25, 2011 at 20:40, Darren Hart wrote:
>> On 05/25/2011 09:49 AM, Henning Heinold wrote:
>>> I agree with khem, each machine should maintain it's bootloader in his bsp
>>> or layer.
>>
>> I'm leaning this way as well. I think oe-core sh
On 05/26/2011 12:58 AM, Jason Kridner wrote:
> On May 26, 2011, at 12:02 AM, Darren Hart
> wrote:
>
>> In order to facilitate reuse of the oe-core u-boot recipe, there
>> needs to be some assurance that the oe-core version won't change
>> without a clear indicator to people extending it.
>>
>>
On 05/26/2011 12:47 AM, Jason Kridner wrote:
> I think this is a good change. One comment below...
>
> On May 26, 2011, at 12:02 AM, Darren Hart wrote:
>
>> oe-core does not define any machines, so it does not make sense to
>> add machine specific information in the oe-core u-boot recipe and
>
On Thu, 2011-05-26 at 21:02 +0800, Lu, Lianhao wrote:
> Maybe all the recipes are using the PKGV default value (?= ${PV}, so
> this just happens to make EXTENDPKGV equal to EXTENDPV.
Yes, could be. The most common situation where PKGV != PV is when
something like gitpkgv.bbclass is in use, which
Phil Blundell wrote on 2011-05-26:
> On Thu, 2011-05-26 at 20:43 +0800, Lu, Lianhao wrote:
>> The problem is that in OE-core the default -deb/-dbg packages are
>> all using EXTENDPV, as well as some other recipes. Do you mean we
>> should make them all using EXTENDPKGV instead of EXTENDPV?
>
> As
On Thu, 2011-05-26 at 20:43 +0800, Lu, Lianhao wrote:
> The problem is that in OE-core the default -deb/-dbg packages are all
> using EXTENDPV, as well as some other recipes. Do you mean we should
> make them all using EXTENDPKGV instead of EXTENDPV?
As far as I can tell, yes, that would be the ri
Phil Blundell wrote on 2011-05-26:
> On Thu, 2011-05-26 at 19:55 +0800, Lianhao Lu wrote:
>> -EXTENDPV = "${EXTENDPEVER}${PV}-${PR}"
>> +EXTENDPV = "${EXTENDPEVER}${PV}-${PKGR}"
>
> That looks a bit weird. Is it really correct to be mixing PV and PKGR like
> that?
>
> FWIW, oe master has:
>
>
Koen Kooi wrote on 2011-05-26:
>
> Op 26 mei 2011, om 13:55 heeft Lianhao Lu het volgende geschreven:
>
>> This is a modification of the original patch to enable network based PR
>> service.
>>
>> The main difference between this series of patch to the original one is
>> that this one uses the
Op 26 mei 2011, om 13:55 heeft Lianhao Lu het volgende geschreven:
> This is a modification of the original patch to enable network based PR
> service.
>
> The main difference between this series of patch to the original one is that
> this one uses the PKGR/PKGV during the package feed creati
On Thu, 2011-05-26 at 19:55 +0800, Lianhao Lu wrote:
> -EXTENDPV = "${EXTENDPEVER}${PV}-${PR}"
> +EXTENDPV = "${EXTENDPEVER}${PV}-${PKGR}"
That looks a bit weird. Is it really correct to be mixing PV and PKGR
like that?
FWIW, oe master has:
EXTENDPE = "${@int('${PE}') and '${PE}_' or ''}"
EXTEN
1. change BB_SIGNATURE_HANDLER from basic to basichash.
2. Added following variables for PR service:
USE_PR_SERV: flag of whether to use the network PR service
PRAUTOINX: search index for the network PR service
PKGV/PKGR: version and revision used in package feed
Signed-off-by: Lianhao Lu
---
m
Added the initial implementation of the server side PR service.
Signed-off-by: Lianhao Lu
---
bitbake/bin/bitbake-prserv | 53 +++
bitbake/lib/prserv/__init__.py | 11 ++
bitbake/lib/prserv/db.py | 100
bitbake/lib/prserv/serv.py | 198 +++
Use PKGV/PKGR to build various package feed in tasks of pacakge_write_xxx.
Signed-off-by: Lianhao Lu
---
meta/classes/package_deb.bbclass |6 +++---
meta/classes/package_ipk.bbclass |6 +++---
meta/classes/package_rpm.bbclass | 10 +-
meta/classes/package_tar.bbclass |4 ++-
This is a modification of the original patch to enable network based PR
service.
The main difference between this series of patch to the original one is that
this one uses the PKGR/PKGV during the package feed creation. It also made the
PR service disabled by default(by leaving the PRSERV_HOST
Setting PRSERV_HOST and PRSERV_PORT would trigger the poky to use remote
PR network service. Leaving them unset allow the user to build image
without the PR network service
Signed-off-by: Lianhao Lu
---
meta-yocto/conf/local.conf.sample |5 +
1 files changed, 5 insertions(+), 0 deletions
1. Added package_get_auto_pr to PACKAGEFUNCS to get the auto
incremented value(PRAUTO) from remote PR service.
2. use PKGV/PKGR for pkgdata which will be used by package_write_xxx.
3. Added supporting functions in prserv.bbclass.
Signed-off-by: Lianhao Lu
---
meta/classes/package.bbclass | 5
If all the postinsts were successfully run in offline mode, and
package-management hasn't been requested as an IMAGE_FEATURE, the opkg
metadata is now redundant and can safely be deleted.
If some packages are still unconfigured at this point then we need to
keep their metadata around so that eithe
On Wed, 2011-05-25 at 22:02 -0700, Darren Hart wrote:
> COMPATIBLE_MACHINES is not easily extended due to
> its regex syntax: "(machine_a|machine_b)", making it difficult to extend the
> u-boot recipe in bbappend files without resorting to machine specific
> overrides.
Not that I have an objectio
On Wed, 2011-05-25 at 18:01 +0100, Phil Blundell wrote:
> Now, leaving aside the question of whether it is reasonable for prelink
> to be depending on transfig,
This also seemed worthy of a bit of further investigation. Here's what
I found out:
The dependency on transfig-native was added by comm
On Wed, 2011-05-25 at 16:08 -0700, Khem Raj wrote:
> while we are talking about fixing native.bbclass on a different
> tangent. I think overrides is another thing we need to fix
> specially libc overrides. When a recipe inherits
> native,cross, or nativesdk then we have to change
> the libc overrid
1 - 100 of 111 matches
Mail list logo