> -Original Message-
> From: Saul Wold [mailto:s...@linux.intel.com]
> Sent: Friday, December 17, 2010 7:19 AM
> To: Yu, Ke
> Cc: Yocto Project Discussion
> Subject: Re: [poky] Recipe Updating Status and call to action
>
> Can you send me a list of the Case C recipes, I would like to revie
Cool.
Thanks a lot!
Would this also be the place where user contributed bsp's (like the
one for kirkwood I posted a while ago) could go in?
Frans
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hi, Jessica and Josh
This is a simple bb class file for generating installer tarball. And thanks for
Lianhao/ke/Dexuan...'s
help which saves me lots of efforts...
It contains below steps:
1. fetch opkg source tarball to download location and copy other six files
(opkg conf, scripts, user con
>From: Garman, Scott A
>Sent: Friday, December 17, 2010 5:57 AM
>
>On 12/15/2010 06:40 PM, Tian, Kevin wrote:
>> On the other hand, along with this I realize that there's one area we need
>> further
>> discuss. How often should we upgrade packages in a given release cycle? MeeGo
>> only does once.
On 12/16/2010 06:17 AM, Yu, Ke wrote:
Thanks Saul for working out this list.
I am a bit surprised on the large number of to-be-upgraded list: 160, because
according to our plan, we actually upgrade most of the recipes in M2, and only
a small number of recipes are supposed to be left for M3. To
Hello All,
Recently Richard sent around an email proposing that a new repository be
created for hosting layers that are not part of the core Yocto Metadata.
This new repository "poky-extras" can host different contributed layers
and will be open to any one.
From Richard's proposed ground r
On 12/15/2010 06:40 PM, Tian, Kevin wrote:
On the other hand, along with this I realize that there's one area we need
further
discuss. How often should we upgrade packages in a given release cycle? MeeGo
only does once. For Yocto we want to keep our recipes in cutting-edge which is
why we schedu
On Thu, Dec 16, 2010 at 12:36 PM, Tim Bird wrote:
> For those interested in my build saga,
> I performed a mostly successful build of poky-minimal-image
> on my old Fedora 8 distro (oustide my Sony firewall).
>
> This was after I installed an poky 586 sdk, and set
> path to include /opt/poky/.../u
For those interested in my build saga,
I performed a mostly successful build of poky-minimal-image
on my old Fedora 8 distro (oustide my Sony firewall).
This was after I installed an poky 586 sdk, and set
path to include /opt/poky/.../usr/bin (to pick up python 2.6.5)
and after adding a fedora pa
Folks,
We have forked M2 off to builds/milestone now and master is open again
for M3 integration.
M2 will take specific and targeted changes for stability and critical
bug fixing.
Master is available for Bug Fixing, Recipe updating and new feature support.
--
Sau!
Saul Wold
Yocto Co
Thanks Saul for working out this list.
I am a bit surprised on the large number of to-be-upgraded list: 160, because
according to our plan, we actually upgrade most of the recipes in M2, and only
a small number of recipes are supposed to be left for M3. To find out the
reason why, PRC team col
Hi, Jessica
Another thing is that after we bitbake the tarball, since bitbake will help us
to do_unpack, so untar opkg is not needed actually. After bitbake job is
finished,
I will change the installer script code to remove untar opkg tarball steps.
Thanks& Regards,
criping
_
12 matches
Mail list logo
