From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [oe] RFC: meta-oe appends and overlayed recipes
Date: Tue, 12 Feb 2013 13:59:14 -0600 [thread overview]
Message-ID: <511A9F12.2020100@windriver.com> (raw)
In-Reply-To: <CABcZAN=ZXF=mLKzd7EswuFj4FLO5WosnciFUjSLst3uZE38wKA@mail.gmail.com>
On 2/12/13 1:32 PM, Chris Larson wrote:
>
> On Tue, Feb 12, 2013 at 12:19 PM, Martin Jansa <martin.jansa@gmail.com
> <mailto:martin.jansa@gmail.com>> wrote:
>
> > * meta-oe/recipes-qt/qt4/qt4-x11-free_4.8.4.bbappend
> > * meta-oe/recipes-qt/qt4/qt4-embedded_4.8.4.bbappend
> > These two add MySQL and PostgreSQL support to Qt and Qt/Embedded. I see this
> > as a distro policy decision; these should move to the layers for whichever
> > distros want this. FWIW, this is particularly egregious if you've already
> > built Qt, then add meta-oe and find Qt is being unexpectedly rebuilt.
>
> MySQL and PostgreSQL are not in oe-core so it cannot be replaced with
> simple PACKAGECONFIG option in oe-core recipe, but I also prefer to
> share such .bbappend somewhere instead of every distribution reinventing
> the wheel when trying to enable something as simple as db in qt.
>
>
> I don't see any reason the oe-core recipe couldn't provide the packageconfig
> options, even missing the dependencies. They are valid package configuration
> options, so they should exist in PACKAGECONFIG. If a distro wants to enable one
> of them, however, they'd better include the layers that provide the deps :)
RPM and Smart integrations both have configuration options that are invalid for
most configurations or sometimes need additional software provided via a layer.
I think this is acceptable, as long as the configuration selects the proper
DEPENDS/RDEPENDS to ensure the items work properly in the end.
--Mark
> --
> Christopher Larson
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
prev parent reply other threads:[~2013-02-12 20:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 17:09 RFC: meta-oe appends and overlayed recipes Paul Eggleton
2013-02-11 17:50 ` Otavio Salvador
2013-02-12 8:38 ` Anders Darander
2013-02-11 22:35 ` Richard Purdie
2013-02-12 9:24 ` Paul Eggleton
2013-02-12 13:10 ` Richard Purdie
2013-02-12 13:38 ` Paul Eggleton
2013-02-12 10:24 ` [oe] " Burton, Ross
2013-02-12 10:38 ` Paul Eggleton
2013-02-12 16:43 ` Otavio Salvador
2013-02-12 20:51 ` Burton, Ross
2013-02-12 21:22 ` Martin Jansa
2013-02-12 21:36 ` Burton, Ross
2013-02-12 21:40 ` Otavio Salvador
2013-02-12 21:53 ` Eric Bénard
2013-02-12 22:02 ` Burton, Ross
2013-02-12 15:50 ` Ross Burton
2013-02-12 16:44 ` Otavio Salvador
2013-02-12 16:53 ` Paul Eggleton
2013-02-12 19:19 ` Martin Jansa
2013-02-12 19:31 ` [oe] " Otavio Salvador
2013-02-12 19:32 ` Paul Eggleton
2013-02-12 19:51 ` Martin Jansa
2013-02-12 20:40 ` Marcin Juszkiewicz
2013-02-12 19:32 ` [oe] " Chris Larson
2013-02-12 19:59 ` Mark Hatle [this message]
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=511A9F12.2020100@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox