From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-devel@lists.openembedded.org,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] qt4 moves out of oe-core - to meta-qt4, or to meta-oe?
Date: Mon, 16 Nov 2015 11:43:30 +0200 [thread overview]
Message-ID: <5649A542.8000307@linux.intel.com> (raw)
In-Reply-To: <20151113114617.GB2567@jama>
On 11/13/2015 01:46 PM, Martin Jansa wrote:
>>>> 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.
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
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-devel@lists.openembedded.org,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] qt4 moves out of oe-core - to meta-qt4, or to meta-oe?
Date: Mon, 16 Nov 2015 11:43:30 +0200 [thread overview]
Message-ID: <5649A542.8000307@linux.intel.com> (raw)
In-Reply-To: <20151113114617.GB2567@jama>
On 11/13/2015 01:46 PM, Martin Jansa wrote:
>>>> 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.
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
next prev parent reply other threads:[~2015-11-16 9:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 16:45 qt4 moves out of oe-core - to meta-qt4, or to meta-oe? alexander.kanavin
2015-11-12 17:03 ` [OE-core] " Andreas Müller
2015-11-12 17:03 ` Andreas Müller
2015-11-12 19:08 ` [OE-core] " Paul Eggleton
2015-11-12 19:08 ` Paul Eggleton
2015-11-13 11:39 ` [OE-core] " Otavio Salvador
2015-11-13 11:39 ` [oe] " Otavio Salvador
2015-11-13 11:46 ` [OE-core] " Martin Jansa
2015-11-13 11:46 ` [oe] " Martin Jansa
2015-11-16 9:43 ` Alexander Kanavin [this message]
2015-11-16 9:43 ` Alexander Kanavin
2015-11-16 10:07 ` [OE-core] " Andreas Oberritter
2015-11-16 10:07 ` [oe] " Andreas Oberritter
2015-11-16 10:26 ` volunteers for meta-qt4 repo maintenance? Alexander Kanavin
2015-11-18 22:08 ` [OE-core] " Paul Eggleton
2015-11-18 22:08 ` Paul Eggleton
2015-11-16 11:20 ` [OE-core] qt4 moves out of oe-core - to meta-qt4, or to meta-oe? Otavio Salvador
2015-11-16 11:20 ` [oe] " Otavio Salvador
2015-11-16 11:23 ` [OE-core] " Alexander Kanavin
2015-11-16 11:23 ` [oe] " Alexander Kanavin
2015-11-16 11:24 ` [OE-core] " Otavio Salvador
2015-11-16 11:24 ` [oe] " Otavio Salvador
2015-11-16 17:10 ` [OE-core] " akuster808
2015-11-16 17:10 ` [oe] " akuster808
2015-11-16 17:39 ` [OE-core] " Mark Hatle
2015-11-16 17:39 ` [oe] " Mark Hatle
2015-11-12 17:19 ` [OE-core] " Martin Jansa
2015-11-12 17:19 ` Martin Jansa
2015-11-12 17:38 ` [OE-core] " alexander.kanavin
2015-11-12 17:38 ` alexander.kanavin
2015-11-12 18:59 ` [OE-core] " Martin Jansa
2015-11-12 18:59 ` Martin Jansa
2015-11-16 10:37 ` [OE-core] " Burton, Ross
2015-11-16 10:37 ` [oe] " Burton, Ross
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=5649A542.8000307@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
/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: link
Be 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.