Have you ever heard about project budgets and that updating a toolchain requires a lot of testing, and hence time, money, man power?
On Mon, Jul 29, 2013 at 11:46 AM, Paul Barker <p...@paulbarker.me.uk> wrote: > On 29 July 2013 11:42, Laszlo Papp <lp...@kde.org> wrote: > > Not to mention, you would cause a "runtime" issue which is pretty simple > to > > fix for a very minor portion compared to a *large* user base using older > > toolchains. There is a huge difference between a few people cannot use > > rfkill for those applications (2, ridiculous), and that a slightly old > > toolchain cannot even build the *whole* project. > > > > Is there any reason that you need to use such an old toolchain? We > can't expect everything we have to compile with every toolchain > release since the start of the GNU project so we need to draw the line > somewhere. I think the feeling is that we'd draw the line somewhere > after the toolchain you're using (from 2009 IIRC). > > -- > Paul Barker > > Email: p...@paulbarker.me.uk > http://www.paulbarker.me.uk >
_______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
