[OE-core] [PATCH] qt4: update to latest version 4.7.4

[Richard Purdie]

On Fri, 2011-09-16 at 13:54 +0100, Phil Blundell wrote:
> On Fri, 2011-09-16 at 14:22 +0200, Eric Bénard wrote:
> > I don't understand why oe-core's development has to be stopped by yocto's 
> > releases process but I may not have found the right page on the wiki 
> > explaining all the details : may you please give me some links concerning this 
> > policy ?
> 
> It does seem a little bit strange, yes.  If it's just a short period
> then I don't think there should be any real problem with granting yocto
> a short freeze in oe-core so that they can do their branching.  
> 
> Of course, this isn't going to scale very well if every user of oe-core
> starts asking for a development freeze so that they can cut their own
> release branches, and it isn't totally obvious to me that yocto couldn't
> just as easily have branched from some semi-arbitrary point and then
> cherry-picked or reverted a few changes to get to where they wanted.  
> 
> Possibly the intent is to make a standalone release of oe-core itself on
> the back of whatever yocto ends up shipping, I dunno.  That seems like
> it might be a reasonable enough way to get a version of OE-core that
> other people can build on without having to repeat all the QA and
> release engineering work that yocto are presumably doing for themselves.

That is exactly what the thought is and its hoped that it will benefit
users. Having some changes of pace and focus (bugfix vs features) to the
development cycle will hopefully be a significant benefit although I
appreciate it will take some getting used to since we've never done it
before. Its only once every six months and only for a few weeks so I
don't think it should be too disruptive...

Cheers,

Richard