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 the shebang. e.g. /bin/env python2.6
On Wed, 2011-07-13 at 05:08 +0800, Richard Purdie wrote: > On Tue, 2011-07-12 at 12:01 -0700, Darren Hart wrote: > > > > On 07/12/2011 11:51 AM, Joshua Lock wrote: > > > 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 6th[1], the same month in > > > which both Ubuntu and Fedora have new releases planned[2,3]. > > > OpenSUSE doesn't have a release scheduled until November 10th[4]. > > > > > > We should accommodate for these releases in our planning around 1.1 as > > > we need to ensure that Yocto 1.1 can be used on the new versions of the > > > chosen supported distros. > > > > > > I had initially suggested we have people doing test and any relevant > > > development around the beta cycles of Ubuntu and Fedora: > > > > > > Fedora Beta (2011-09-20) > > > Ubuntu (2011-09-01) > > > In this time frame OpenSUSE will be on Milestone 5 (2011-09-01) which > > > afaict (based on the 6th milestone being followed by an RC) should > > > roughly equate to a beta. > > > > > > However this aligns with our RC period at which point we may not want to > > > accept large patches? > > > > > > To meet our stabilise complete goal of August 29th we'd have to have > > > people testing with: > > > Fedora Alpha (2011-08-16) > > > Ubuntu Alpha 3 (2011-08-04) > > > OpenSUSE Milestone 4 (2011-08-11) > > > > > > What are peoples thoughts on this? > > > > 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 isn't something I > > think we should spend too much time on. Minor fixes to support these > > post release seem like good candidates for a point release. > > 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 with a significant portion of > people who do stay close to the edge as far as distros go. They'll take > latest releases and expect Yocto to work on them even if the releases > come out at the same time. Its not often realised how far in advance > trees get frozen for stabilisation. > > So summary is I'm in favour of trying to identify problems early and > then doing what we can to address them... > > As such, this time around I'll update my build machine to latest Ubuntu > at the beginning of August.... > > Cheers, > > Richard > > _______________________________________________ > yocto mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/yocto -- 倪庆亮 TEL: 13588371863 E-MAIL: [email protected] BLOG: http://niqingliang2003.wordpress.com _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
