yocto@lists.yoctoproject.org

Re: Supporting upcoming distribution releases

These are both valid on Fedora 15, iirc before distributions started shipping Python 3 they were less common though... Patches welcome :-) I looked at it briefly and the work would require more time

By Joshua Lock <josh@...> · #1831 ·

Re: Supporting upcoming distribution releases

/usr/bin/env python2 /usr/bin/env python2.7 both of them are ok for archlinux, but I don't know which is ok for other distributions, maybe both are not. maybe we can make a shell script to detect

By niqingliang · #1830 ·

Re: Supporting upcoming distribution releases

I looked at this but not enough of the distributions we care to support have a python2.6 binary: joshual@scimitar:~ $ /usr/bin/env python2 Python 2.7.1 (r271:86832, Apr 12 2011, 16:16:18) [GCC 4.6.0

By Joshua Lock <josh@...> · #1829 ·

Re: Supporting upcoming distribution releases

I think Archlinux is the preferred choice.-_- Just joke. I doubt why the bitbake need python2.x but just use /bin/env python. I think If it need a specific version python, it should write it in

By niqingliang · #1828 ·

[PATCH 2/2][KERNEL] meta-fri2: use iwlagn feature

From: Tom Zanussi <tom.zanussi@...> Make use of the Intel wireless support for the Intel 6205 ABGN. Signed-off-by: Tom Zanussi <tom.zanussi@...> ---

By tom.zanussi@... · #1826 ·

[PATCH 1/2][KERNEL] meta: add mac80211 and iwlagn features

From: Tom Zanussi <tom.zanussi@...> Add iwlagn feature (Intel Wirelss WiFi Next Gen AGN) and one of its dependencies, mac80211, as a feature, since there are a bunch of other config items that

By tom.zanussi@... · #1825 ·

[PATCH 0/2][KERNEL] Add and use iwlagn and mac80211 features

From: Tom Zanussi <tom.zanussi@...> This patchset adds a couple new features, iwlagn and mac80211 for the fri2 BSP. Please pull into linux-yocto-dev. Pull URL:

By tom.zanussi@... · #1827 ·

Re: Supporting upcoming distribution releases

Much as I'd like to agree with you, traditionally this does tend to bite us hard. The fixes some of the releases have needed are sometimes not so minor too :(. The reason is that we have a community

By Richard Purdie · #1824 ·

Re: Supporting upcoming distribution releases

That is a great idea! -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel

By Darren Hart <dvhart@...> · #1823 ·

Re: [PATCH 0/1]meta/routerstationpro: remove some conflicted configurations

Not for the kernel, we explicitly don't want them in the kernel tree. I'll make sure the appropriate bugs get updated in the tracker. Bruce

By Bruce Ashfield <bruce.ashfield@...> · #1822 ·

Re: [PATCH 0/1]meta/routerstationpro: remove some conflicted configurations

The Bug fix info needs to go into the commit message, not as part of the email header as it will get lost here. Thanks Sau!

By Saul Wold <sgw@...> · #1821 ·

Re: Supporting upcoming distribution releases

I understand what you're saying but I think the stance bears further consideration because our release is so close to that of the distributions and because so many of our target users will upgrade

By Joshua Lock <josh@...> · #1820 ·

Minutes: Yocto Technical Team (Tuesday, July 12, 2011 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada))

Attendees: Dave, Paul, Darren, Jeff, Dirk, Richard, Josh, Tom, Koen, Saul, Mark, Denys, Jason, Beth, Song Action item list: * Team: please take a look at the proposed post 1.1 items (yellow in

By Liu, Song <song.liu@...> · #1928 ·

Re: Supporting upcoming distribution releases

At the very least a sanity test to know which sorts of issues we'll hit with these would be valuable. However, I believe our policy is N-1, and not N+1,N,N-1, so supporting not-yet released versions

By Darren Hart <dvhart@...> · #1819 ·

Supporting upcoming distribution releases

In our technical team call today we spent some time discussing how to support distribution releases that are due to happen around the time of Yocto 1.1. Yocto 1.1 is scheduled for release on October

By Joshua Lock <josh@...> · #1818 ·

[PATCH] DOCS: Rename "poky-init-build-env" to "oe-init-build-env"

Adjust a couple doc files to reflect that the older poky-init-build-env command has been renamed to oe-init-build-env. Signed-off-by: Robert P. J. Day <rpjday@...> --- diff --git

By Robert P. J. Day · #1817 ·

Re: should dev docs replace "poky-init-build-env" with "oe-init-build-env"?

It did get renamed as you describe, yes. I don't think anyone has a patch so I'd gladly take one, thanks! Richard

By Richard Purdie · #1816 ·

should dev docs replace "poky-init-build-env" with "oe-init-build-env"?

poking around my git clone and i notice a few references to what *seems* to be the older script for init'ing the build environment in the documentation directory: $ grep -rw poky-init-build-env

By Robert P. J. Day · #1815 ·

Re: Menu configuration

At present there is not any interactive menu based configuration but there is work ongoing on a UI called hob which allows you to select packages and construct images of those packages so its a

By Richard Purdie · #1814 ·

Re: [PATCH][poky-extras] meta-kernel-dev: allow for dangling bbappend files

Agreed. This is the right solution. Acked-by: Bruce Ashfield <bruce.ashfield@...>

By Bruce Ashfield <bruce.ashfield@...> · #1813 ·

Messages