All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Cc: 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: Fri, 13 Nov 2015 09:39:15 -0200	[thread overview]
Message-ID: <CAP9ODKqk4B_i+59asEqoVNjkynBWTACD0cM4f0JdxMCopprTkA@mail.gmail.com> (raw)
In-Reply-To: <4335862.fNWyiaI9Bu@peggleto-mobl.ger.corp.intel.com>

On Thu, Nov 12, 2015 at 5:08 PM, Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
> On Thursday 12 November 2015 18:03:27 Andreas Müller wrote:
>> On Thu, Nov 12, 2015 at 5:45 PM,  <alexander.kanavin@linux.intel.com> 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
>> > .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?
>>
>> 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.

-- 
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


WARNING: multiple messages have this Message-ID (diff)
From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Cc: 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: Fri, 13 Nov 2015 09:39:15 -0200	[thread overview]
Message-ID: <CAP9ODKqk4B_i+59asEqoVNjkynBWTACD0cM4f0JdxMCopprTkA@mail.gmail.com> (raw)
In-Reply-To: <4335862.fNWyiaI9Bu@peggleto-mobl.ger.corp.intel.com>

On Thu, Nov 12, 2015 at 5:08 PM, Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
> On Thursday 12 November 2015 18:03:27 Andreas Müller wrote:
>> On Thu, Nov 12, 2015 at 5:45 PM,  <alexander.kanavin@linux.intel.com> 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
>> > .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?
>>
>> 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.

-- 
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


  reply	other threads:[~2015-11-13 11:39 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 ` Andreas Müller
2015-11-12 17:03   ` [OE-core] " Andreas Müller
2015-11-12 19:08   ` Paul Eggleton
2015-11-12 19:08     ` [OE-core] " Paul Eggleton
2015-11-13 11:39     ` Otavio Salvador [this message]
2015-11-13 11:39       ` Otavio Salvador
2015-11-13 11:46       ` [oe] " Martin Jansa
2015-11-13 11:46         ` [OE-core] " Martin Jansa
2015-11-16  9:43         ` [oe] " Alexander Kanavin
2015-11-16  9:43           ` [OE-core] " Alexander Kanavin
2015-11-16 10:07           ` [oe] " Andreas Oberritter
2015-11-16 10:07             ` [OE-core] " Andreas Oberritter
2015-11-16 10:26             ` volunteers for meta-qt4 repo maintenance? Alexander Kanavin
2015-11-18 22:08               ` Paul Eggleton
2015-11-18 22:08                 ` [OE-core] " Paul Eggleton
2015-11-16 11:20           ` [oe] qt4 moves out of oe-core - to meta-qt4, or to meta-oe? Otavio Salvador
2015-11-16 11:20             ` [OE-core] " Otavio Salvador
2015-11-16 11:23             ` [oe] " Alexander Kanavin
2015-11-16 11:23               ` [OE-core] " Alexander Kanavin
2015-11-16 11:24               ` [oe] " Otavio Salvador
2015-11-16 11:24                 ` [OE-core] " Otavio Salvador
2015-11-16 17:10                 ` [oe] " akuster808
2015-11-16 17:10                   ` [OE-core] " akuster808
2015-11-16 17:39                   ` [oe] " Mark Hatle
2015-11-16 17:39                     ` [OE-core] " Mark Hatle
2015-11-12 17:19 ` Martin Jansa
2015-11-12 17:19   ` [OE-core] " Martin Jansa
2015-11-12 17:38   ` alexander.kanavin
2015-11-12 17:38     ` [OE-core] " alexander.kanavin
2015-11-12 18:59     ` Martin Jansa
2015-11-12 18:59       ` [OE-core] " Martin Jansa
2015-11-16 10:37       ` [oe] " Burton, Ross
2015-11-16 10:37         ` [OE-core] " 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=CAP9ODKqk4B_i+59asEqoVNjkynBWTACD0cM4f0JdxMCopprTkA@mail.gmail.com \
    --to=otavio.salvador@ossystems.com.br \
    --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.