[yocto] [Package Report System]Upgrade recipes name list

2013-10-13 Thread Yocto Project Package Report System
This mail was sent out by Package Report System. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this recipe remainder until newer u

[yocto] [Package Report System]Manual check recipes name list

2013-10-13 Thread Yocto Project Package Report System
This mail was sent out by Package Report System. It will list all the recipes which can't check upstream version by script, and will show how long it is since their last mannual version check. You can check the detail information at http://packages.yoctoproject.org/manuallychkinfo PackageName

[yocto] Image Library(IMGLIB) with Yocto

2013-10-13 Thread Zafrullah Syed
Hi, Is there any guide on how to get TMS320C6000 Image Library (IMGLIB) into Yocto?  Regards, Zafrullah ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] DISTRO_FEATURES and shared SSTATE

2013-10-13 Thread Chris Larson
On Sun, Oct 13, 2013 at 8:04 AM, seth bollinger wrote: > How does yocto know which package version to choose for an image if the > package can be altered (compilation difference, or perhaps config > alteration, etc.) by a DISTRO_FEATURE? > > For instance, if I make a change to sysvinit-inittab/in

[yocto] DISTRO_FEATURES and shared SSTATE

2013-10-13 Thread seth bollinger
Hello All, How does yocto know which package version to choose for an image if the package can be altered (compilation difference, or perhaps config alteration, etc.) by a DISTRO_FEATURE? For instance, if I make a change to sysvinit-inittab/inittab based on a DISTRO_FEATURE, I can have multi