From: akuster808 <akuster808@gmail.com> To: "Burton, Ross" <ross.burton@intel.com>, OE-core <openembedded-core@lists.openembedded.org>, openembedded-devel@lists.openembedded.org Subject: Re: Future of Qt4 recipes Date: Tue, 23 Jun 2015 16:13:13 -0700 [thread overview] Message-ID: <5589E809.8060000@gmail.com> (raw) In-Reply-To: <CAJTo0LaKEvtznsdfz8gLWFSLyb6Rx2XsgbYG_cfOrAm+W2UfEg@mail.gmail.com> On 06/22/2015 03:43 AM, Burton, Ross wrote: > Hi, > > So, Qt 4.8.7 was released last month[1]. Support for Qt4 stops at the > end of 2015, and 4.8.7 is planned to be the last ever release of Qt4. > It's still mandated by the long-awaited LSB 5 but I think it's fair to > say that the majority of developers have moved to Qt5. So, what should > we do with Qt4 moving forward?[2] I see several options: > > 1) There's still lots of people using Qt4 in production, please keep it > in oe-core! (and revisit in six months time) > 2) Move Qt4 recipes and classes to a meta-qt4 layer now so that oe-core > 1.9 ships without Qt4, and anyone wanting full LSB compliance or Qt4 > will need to add that layer to their distro. > > Personally, I vote for (2). Any other comments? #2 sounds fine. would recipes-lsb move out to its own layer too? - Armin > > Ross > > [1] https://blog.qt.io/blog/2015/05/26/qt-4-8-7-released/ > [2] https://bugzilla.yoctoproject.org/show_bug.cgi?id=7812 > >
WARNING: multiple messages have this Message-ID (diff)
From: akuster808 <akuster808@gmail.com> To: "Burton, Ross" <ross.burton@intel.com>, OE-core <openembedded-core@lists.openembedded.org>, openembedded-devel@lists.openembedded.org Subject: Re: [OE-core] Future of Qt4 recipes Date: Tue, 23 Jun 2015 16:13:13 -0700 [thread overview] Message-ID: <5589E809.8060000@gmail.com> (raw) In-Reply-To: <CAJTo0LaKEvtznsdfz8gLWFSLyb6Rx2XsgbYG_cfOrAm+W2UfEg@mail.gmail.com> On 06/22/2015 03:43 AM, Burton, Ross wrote: > Hi, > > So, Qt 4.8.7 was released last month[1]. Support for Qt4 stops at the > end of 2015, and 4.8.7 is planned to be the last ever release of Qt4. > It's still mandated by the long-awaited LSB 5 but I think it's fair to > say that the majority of developers have moved to Qt5. So, what should > we do with Qt4 moving forward?[2] I see several options: > > 1) There's still lots of people using Qt4 in production, please keep it > in oe-core! (and revisit in six months time) > 2) Move Qt4 recipes and classes to a meta-qt4 layer now so that oe-core > 1.9 ships without Qt4, and anyone wanting full LSB compliance or Qt4 > will need to add that layer to their distro. > > Personally, I vote for (2). Any other comments? #2 sounds fine. would recipes-lsb move out to its own layer too? - Armin > > Ross > > [1] https://blog.qt.io/blog/2015/05/26/qt-4-8-7-released/ > [2] https://bugzilla.yoctoproject.org/show_bug.cgi?id=7812 > >
next prev parent reply other threads:[~2015-06-23 23:13 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-22 10:43 Future of Qt4 recipes Burton, Ross 2015-06-22 10:43 ` Burton, Ross 2015-06-22 14:27 ` Otavio Salvador 2015-06-22 14:27 ` [OE-core] " Otavio Salvador 2015-06-22 21:48 ` Florian Boor 2015-06-22 21:58 ` Philip Balister 2015-06-22 22:14 ` Burton, Ross 2015-06-22 22:50 ` Philip Balister 2015-06-23 23:13 ` akuster808 [this message] 2015-06-23 23:13 ` [OE-core] " akuster808 2015-06-24 0:26 ` Martin Jansa 2015-06-24 0:26 ` [OE-core] " Martin Jansa
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=5589E809.8060000@gmail.com \ --to=akuster808@gmail.com \ --cc=openembedded-core@lists.openembedded.org \ --cc=openembedded-devel@lists.openembedded.org \ --cc=ross.burton@intel.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.