From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] Remove vala from oe-core
Date: Thu, 12 Nov 2015 13:18:04 +0200 [thread overview]
Message-ID: <5644756C.2060607@linux.intel.com> (raw)
In-Reply-To: <1447262253.3559.249.camel@linuxfoundation.org>
On 11/11/2015 07:17 PM, Richard Purdie wrote:
>>
>> If this class is moved to meta-vala, how do you make packages in oe-core
>> inherit it, or otherwise do what it does?
>
> Much as I dislike this, you could do something like:
>
> inherit ${@base_contains('PACKAGECONFIG', 'vala', 'vala', '')}
Ugh, yes. It's an optional circular dependency and an opaque side effect
rolled in one.
I'd rather go with bbappends in meta-vala (even though having them means
that oe-core has failed to serve the needs of meta-vala users), or just
keep vala in oe-core - it's not big and doesn't have special needs.
Alex
next prev parent reply other threads:[~2015-11-12 11:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 14:22 [RFC] Remove vala from oe-core Jussi Kukkonen
2015-11-10 14:22 ` Jussi Kukkonen
2015-11-10 14:30 ` Alexander Kanavin
2015-11-10 14:29 ` Carlos Rafael Giani
2015-11-10 14:32 ` Alexander Kanavin
2015-11-10 14:50 ` Paul Eggleton
2015-11-10 15:06 ` Alexander Kanavin
2015-11-10 15:09 ` Paul Eggleton
2015-11-10 15:10 ` Burton, Ross
2015-11-10 15:19 ` Alexander Kanavin
2015-11-10 15:29 ` Otavio Salvador
2015-11-10 15:37 ` Alexander Kanavin
2015-11-10 15:39 ` Otavio Salvador
2015-11-10 16:25 ` Andreas Müller
2015-11-10 16:52 ` Otavio Salvador
2015-11-11 17:17 ` Richard Purdie
2015-11-11 17:38 ` Paul Eggleton
2015-11-12 11:18 ` Alexander Kanavin [this message]
2015-11-10 16:02 ` [OE-core] " Martin Jansa
2015-11-10 16:02 ` 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=5644756C.2060607@linux.intel.com \
--to=alexander.kanavin@linux.intel.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 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.