qt4 moves out of oe-core - to meta-qt4, or to meta-oe?
Hello,
now that 2.0 is out, it's time to move the Qt4 recipes out of oe-core. This has been discussed previously here:
http://lists.openembedded.org/pipermail/openembedded-core/2015-June/106355.html
I'm not sure where the recipes should land, and want to ask your opinion. The options are:
1) Make a new layer, meta-qt4, under meta-openembedded tree. Move also everything in meta-oe/recipes-qt (and possibly other spots) to that layer. This is somewhat more disruptive to people's layer configurations, but would clearly separate qt4, and slim down meta-oe.
2) Simply move the qt4 recipes from oe-core to meta-oe/recipes-qt, so they will be next to all the qt4-based software. This is less disruptive, but adds bloat to meta-oe.
Preferences?
Alex
Quoted 13 lines · On Thu, Nov 12, 2015 at 5:45 PM, <[email protected]> wrote:
Hello,
now that 2.0 is out, it's time to move the Qt4 recipes out of oe-core. This has been discussed previously here:
http://lists.openembedded.org/pipermail/openembedded-core/2015-June/106355.htmlI'm not sure where the recipes should land, and want to ask your opinion. The options are:
1) Make a new layer, meta-qt4, under meta-openembedded tree. Move also everything in meta-oe/recipes-qt (and possibly other spots) to that layer. This is somewhat more disruptive to people's layer configurations, but would clearly separate qt4, and slim down meta-oe.
Quoted 6 lines
2) Simply move the qt4 recipes from oe-core to meta-oe/recipes-qt, so they will be next to all the qt4-based software. This is less disruptive, but adds bloat to meta-oe.
Preferences?
1) or even better in a separate repo
Andreas
Quoted 15 lines · On Thursday 12 November 2015 18:03:27 Andreas Müller wrote:
Quoted 14 lines · On Thu, Nov 12, 2015 at 5:45 PM, <[email protected]> wrote:
Hello,
now that 2.0 is out, it's time to move the Qt4 recipes out of oe-core. This has been discussed previously here:
http://lists.openembedded.org/pipermail/openembedded-core/2015-June/106355
.htmlI'm not sure where the recipes should land, and want to ask your opinion. The options are:
1) Make a new layer, meta-qt4, under meta-openembedded tree. Move also everything in meta-oe/recipes-qt (and possibly other spots) to that layer. This is somewhat more disruptive to people's layer configurations, but would clearly separate qt4, and slim down meta-oe.
Quoted 7 lines
Quoted 5 lines
2) Simply move the qt4 recipes from oe-core to meta-oe/recipes-qt, so they will be next to all the qt4-based software. This is less disruptive, but adds bloat to meta-oe.
Preferences?
1) or even better in a separate repo
To be honest, I had anticipated this being a separate meta-qt4 repo myself. It would be consistent with what has been done with Qt 5 and much earlier with Qt 3.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 20 lines · Paul Eggleton
Quoted 19 lines · On Thursday 12 November 2015 18:03:27 Andreas Müller wrote:
Quoted 18 lines · On Thu, Nov 12, 2015 at 5:45 PM, <[email protected]> wrote:
Hello,
now that 2.0 is out, it's time to move the Qt4 recipes out of oe-core. This has been discussed previously here:
http://lists.openembedded.org/pipermail/openembedded-core/2015-June/106355
.htmlI'm not sure where the recipes should land, and want to ask your opinion. The options are:
1) Make a new layer, meta-qt4, under meta-openembedded tree. Move also everything in meta-oe/recipes-qt (and possibly other spots) to that layer. This is somewhat more disruptive to people's layer configurations, but would clearly separate qt4, and slim down meta-oe.2) Simply move the qt4 recipes from oe-core to meta-oe/recipes-qt, so they will be next to all the qt4-based software. This is less disruptive, but adds bloat to meta-oe.
Quoted 7 lines
Quoted 3 lines
Quoted 1 line
Preferences?
1) or even better in a separate repo
To be honest, I had anticipated this being a separate meta-qt4 repo myself. It would be consistent with what has been done with Qt 5 and much earlier with Qt 3.
Agreed.
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 24 lines · Otavio Salvador
Quoted 22 lines · Paul Eggleton
Quoted 21 lines · On Thursday 12 November 2015 18:03:27 Andreas Müller wrote:
Quoted 19 lines · On Thu, Nov 12, 2015 at 5:45 PM, <[email protected]> wrote:
Hello,
now that 2.0 is out, it's time to move the Qt4 recipes out of oe-core. This has been discussed previously here:
http://lists.openembedded.org/pipermail/openembedded-core/2015-June/106355
.htmlI'm not sure where the recipes should land, and want to ask your opinion. The options are:
1) Make a new layer, meta-qt4, under meta-openembedded tree. Move also everything in meta-oe/recipes-qt (and possibly other spots) to that layer. This is somewhat more disruptive to people's layer configurations, but would clearly separate qt4, and slim down meta-oe.2) Simply move the qt4 recipes from oe-core to meta-oe/recipes-qt, so they will be next to all the qt4-based software. This is less disruptive, but adds bloat to meta-oe.
Preferences?
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
1) or even better in a separate repo
To be honest, I had anticipated this being a separate meta-qt4 repo myself. It would be consistent with what has been done with Qt 5 and much earlier with Qt 3.
Agreed.
I'm also fine with separate layer.
Even better for me, I'll be less tempted to include it in my world builds and to fix qt-mobility-* issues.
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 6 lines · Martin Jansa
Quoted 6 lines
Quoted 5 lines
Quoted 1 line
1) or even better in a separate repo
To be honest, I had anticipated this being a separate meta-qt4 repo myself. It would be consistent with what has been done with Qt 5 and much earlier with Qt 3.
Quoted 6 lines
Quoted 1 line
Agreed.
I'm also fine with separate layer.
Even better for me, I'll be less tempted to include it in my world builds and to fix qt-mobility-* issues.
Making a separate repository with this layer is even more disruptive, and complicates administration and maintenance. I'm not going to handle those. So I'll make a meta-qt4 layer under meta-oe, and it's fine if there is no official maintainer or ongoing build testing for it at least until someone volunteers to pick it up.
Alex
Quoted 14 lines · Alexander Kanavin
Quoted 12 lines · Martin Jansa
Quoted 9 lines
Quoted 7 lines
Quoted 1 line
1) or even better in a separate repo
To be honest, I had anticipated this being a separate meta-qt4 repo myself. It
would be consistent with what has been done with Qt 5 and much earlier with
Qt 3.Agreed.
I'm also fine with separate layer.
Quoted 8 lines
Quoted 2 lines
Even better for me, I'll be less tempted to include it in my world builds and to fix qt-mobility-* issues.
Making a separate repository with this layer is even more disruptive, and complicates administration and maintenance. I'm not going to handle those. So I'll make a meta-qt4 layer under meta-oe, and it's fine if there is no official maintainer or ongoing build testing for it at least until someone volunteers to pick it up.
Basically everyone agreed on moving qt4 to its own repo. And your conclusion is to ignore that and move qt4 to meta-openembedded, already expecting bitrot?
Regards,
Andreas
volunteers for meta-qt4 repo maintenance?
Quoted 9 lines · Andreas Oberritter
Quoted 5 lines
Making a separate repository with this layer is even more disruptive, and complicates administration and maintenance. I'm not going to handle those. So I'll make a meta-qt4 layer under meta-oe, and it's fine if there is no official maintainer or ongoing build testing for it at least until someone volunteers to pick it up.
Basically everyone agreed on moving qt4 to its own repo. And your conclusion is to ignore that and move qt4 to meta-openembedded, already expecting bitrot?
Are you willing to be the maintainer of that separate repo? So far no one has stepped up for this job. In this situation, it's better to keep the recipes under meta-openembedded tree and mark them as unmaintained.
I'll ask this explicitly - any volunteers for a separate meta-qt4 repository and layer maintenance?
Alex
Re: volunteers for meta-qt4 repo maintenance?
Quoted 11 lines · On Monday 16 November 2015 12:26:05 Alexander Kanavin wrote:
Quoted 9 lines · Andreas Oberritter
Quoted 5 lines
Making a separate repository with this layer is even more disruptive, and complicates administration and maintenance. I'm not going to handle those. So I'll make a meta-qt4 layer under meta-oe, and it's fine if there is no official maintainer or ongoing build testing for it at least until someone volunteers to pick it up.
Basically everyone agreed on moving qt4 to its own repo. And your conclusion is to ignore that and move qt4 to meta-openembedded, already expecting bitrot?
Quoted 6 lines
Are you willing to be the maintainer of that separate repo? So far no one has stepped up for this job. In this situation, it's better to keep the recipes under meta-openembedded tree and mark them as unmaintained.
I'll ask this explicitly - any volunteers for a separate meta-qt4 repository and layer maintenance?
Put my name against it if you need a name - no promises on how active I'll be though. I will definitely volunteer to do the initial move-out and repo creation so you wouldn't need to do anything.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 21 lines · Alexander Kanavin
Quoted 10 lines · Martin Jansa
Quoted 10 lines
Quoted 8 lines
Quoted 1 line
1) or even better in a separate repo
To be honest, I had anticipated this being a separate meta-qt4 repo myself. It
would be consistent with what has been done with Qt 5 and much earlier with
Qt 3.Quoted 7 lines
Quoted 1 line
Agreed.
I'm also fine with separate layer.
Even better for me, I'll be less tempted to include it in my world builds and to fix qt-mobility-* issues.
Quoted 5 lines
Making a separate repository with this layer is even more disruptive, and complicates administration and maintenance. I'm not going to handle those. So I'll make a meta-qt4 layer under meta-oe, and it's fine if there is no official maintainer or ongoing build testing for it at least until someone volunteers to pick it up.
I will nack the patch to include it onto meta-oe; I also guess that Martin will also nack it.
Make it another layer as suggested, please.
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 10 lines · Otavio Salvador
Quoted 5 lines
Making a separate repository with this layer is even more disruptive, and complicates administration and maintenance. I'm not going to handle those. So I'll make a meta-qt4 layer under meta-oe, and it's fine if there is no official maintainer or ongoing build testing for it at least until someone volunteers to pick it up.
I will nack the patch to include it onto meta-oe; I also guess that Martin will also nack it.
Make it another layer as suggested, please.
A separate layer under meta-openembedded or a separate repository with the layer? Please be clear.
Alex
Quoted 11 lines · Alexander Kanavin
Quoted 9 lines · Otavio Salvador
Quoted 7 lines
Making a separate repository with this layer is even more disruptive, and complicates administration and maintenance. I'm not going to handle those.
So I'll make a meta-qt4 layer under meta-oe, and it's fine if there is no official maintainer or ongoing build testing for it at least until someone
volunteers to pick it up.
Quoted 8 lines
Quoted 4 lines
I will nack the patch to include it onto meta-oe; I also guess that Martin will also nack it.
Make it another layer as suggested, please.
A separate layer under meta-openembedded or a separate repository with the layer? Please be clear.
Another repository.
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 16 lines · Otavio Salvador
Quoted 14 lines · Alexander Kanavin
Quoted 12 lines · Otavio Salvador
Quoted 7 lines
Making a separate repository with this layer is even more disruptive, and complicates administration and maintenance. I'm not going to handle those.
So I'll make a meta-qt4 layer under meta-oe, and it's fine if there is no official maintainer or ongoing build testing for it at least until someone
volunteers to pick it up.I will nack the patch to include it onto meta-oe; I also guess that Martin will also nack it.
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Make it another layer as suggested, please.
A separate layer under meta-openembedded or a separate repository with the layer? Please be clear.
Another repository.
Agree with a separate repo. It clarifies our intention and implies nothing.
Quoted 1 line
Quoted 22 lines · On 11/16/15 11:10 AM, akuster808 wrote:
Quoted 19 lines · Otavio Salvador
Quoted 17 lines · Alexander Kanavin
Quoted 13 lines · Otavio Salvador
Quoted 7 lines
Making a separate repository with this layer is even more disruptive, and complicates administration and maintenance. I'm not going to handle those.
So I'll make a meta-qt4 layer under meta-oe, and it's fine if there is no official maintainer or ongoing build testing for it at least until someone
volunteers to pick it up.I will nack the patch to include it onto meta-oe; I also guess that Martin will also nack it.
Make it another layer as suggested, please.
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
A separate layer under meta-openembedded or a separate repository with the layer? Please be clear.
Another repository.
Agree with a separate repo. It clarifies our intention and implies nothing.
I'm fine with a separate repo as well. Then whomever still needs it can work with it as necessary.
--Mark
Quoted 2 lines
Quoted 2 lines
Quoted 13 lines · On Thu, Nov 12, 2015 at 06:45:34PM +0200, [email protected]…
Hello,
now that 2.0 is out, it's time to move the Qt4 recipes out of oe-core. This has been discussed previously here:
http://lists.openembedded.org/pipermail/openembedded-core/2015-June/106355.htmlI'm not sure where the recipes should land, and want to ask your opinion. The options are:
1) Make a new layer, meta-qt4, under meta-openembedded tree. Move also everything in meta-oe/recipes-qt (and possibly other spots) to that layer. This is somewhat more disruptive to people's layer configurations, but would clearly separate qt4, and slim down meta-oe.
Quoted 5 lines
2) Simply move the qt4 recipes from oe-core to meta-oe/recipes-qt, so they will be next to all the qt4-based software. This is less disruptive, but adds bloat to meta-oe.
Preferences?
1)
There is already enough meta-oe bloat moved from oe-core:
http://lists.openembedded.org/pipermail/openembedded-core/2015-November/112665.html
WARN: qt-mobility-embedded: qt-mobility-embedded rdepends on glib-2.0, but it isn't a build dependency?
WARN: qt-mobility-embedded: qt-mobility-embedded rdepends on gstreamer, but it isn't a build dependency?
WARN: qt-mobility-embedded: qt-mobility-embedded rdepends on libasound, but it isn't a build dependency?
WARN: qt-mobility-embedded: qt-mobility-embedded rdepends on libgstapp-0.10, but it isn't a build dependency?
WARN: qt-mobility-embedded: qt-mobility-embedded rdepends on libgstvideo-0.10, but it isn't a build dependency?
WARN: qt-mobility-x11: qt-mobility-x11 rdepends on glib-2.0, but it isn't a build dependency?
WARN: qt-mobility-x11: qt-mobility-x11 rdepends on gstreamer, but it isn't a build dependency?
WARN: qt-mobility-x11: qt-mobility-x11 rdepends on libasound, but it isn't a build dependency?
WARN: qt-mobility-x11: qt-mobility-x11 rdepends on libgstapp-0.10, but it isn't a build dependency?
WARN: qt-mobility-x11: qt-mobility-x11 rdepends on libgstinterfaces-0.10, but it isn't a build dependency?
WARN: qt-mobility-x11: qt-mobility-x11 rdepends on libgstvideo-0.10, but it isn't a build dependency?
WARN: qt-mobility-x11: qt-mobility-x11 rdepends on libxext, but it isn't a build dependency?
WARN: qt-mobility-x11: qt-mobility-x11 rdepends on libxv, but it isn't a build dependency?
I'm still fixing gst-plugins-good and more gst-plugins-bad issues..
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 6 lines
There is already enough meta-oe bloat moved from oe-core:
http://lists.openembedded.org/pipermail/openembedded-core/2015-November/112665.html
WARN: qt-mobility-embedded: qt-mobility-embedded rdepends on glib-2.0, but it isn't a build dependency?
If increasing bloat is a problem, why do recipes in meta-oe need to be maintained indefinitely? Old cruft can be dropped from meta-oe, just as it is dropped from oe-core. Just ask the public if it's ok, set a timeframe, and do it.
qt-mobility in particular has been dead for several years, and doesn't even have official upstream tarballs anymore. Why spend time fixing it?
Alex
Quoted 7 lines · On Thu, Nov 12, 2015 at 07:38:58PM +0200, [email protected]…
Quoted 6 lines
There is already enough meta-oe bloat moved from oe-core:
http://lists.openembedded.org/pipermail/openembedded-core/2015-November/112665.html
WARN: qt-mobility-embedded: qt-mobility-embedded rdepends on glib-2.0, but it isn't a build dependency?
Quoted 7 lines
If increasing bloat is a problem, why do recipes in meta-oe need to be maintained indefinitely? Old cruft can be dropped from meta-oe, just as it is dropped from oe-core. Just ask the public if it's ok, set a timeframe, and do it.
qt-mobility in particular has been dead for several years, and doesn't even have official upstream tarballs anymore. Why spend time fixing it?
That's why there is increasing number of PNBLACKLISTs with each release.
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 11 lines · Martin Jansa
Quoted 3 lines
Quoted 3 lines
There is already enough meta-oe bloat moved from oe-core:
http://lists.openembedded.org/pipermail/openembedded-core/2015-November/112665.html
Quoted 2 lines
Quoted 2 lines
WARN: qt-mobility-embedded: qt-mobility-embedded rdepends on glib-2.0,
but
Quoted 4 lines
Quoted 1 line
it isn't a build dependency?
If increasing bloat is a problem, why do recipes in meta-oe need to be maintained indefinitely? Old cruft can be dropped from meta-oe, just as
Quoted 9 lines
it
Quoted 5 lines
is dropped from oe-core. Just ask the public if it's ok, set a timeframe, and do it.
qt-mobility in particular has been dead for several years, and doesn't even have official upstream tarballs anymore. Why spend time fixing it?
That's why there is increasing number of PNBLACKLISTs with each release.
The recipes were removed from oe-core as they're dead upstream, and basically as a courtesy moved to meta-oe so anyone still using dead software can still build it. If they're just bitrotting and literally nobody is using the recipes then they should be removed: meta-oe isn't a historical archive that you're expected to maintain for the next decade.
Ross