From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking, meta-oe][PATCH 0/9] Move networking recipes to meta-networking
Date: Tue, 16 Apr 2013 14:22:52 +0100 [thread overview]
Message-ID: <2803066.5t2BvEp21p@helios> (raw)
In-Reply-To: <5C3F1A93-CC39-45E6-AF2B-FF29F50C67CD@dominion.thruhere.net>
On Tuesday 16 April 2013 13:30:29 Koen Kooi wrote:
> Op 16 apr. 2013, om 13:19 heeft Paul Eggleton
<paul.eggleton@linux.intel.com> het volgende geschreven:
> > On Tuesday 16 April 2013 13:09:46 Koen Kooi wrote:
> >> These look good to me, but
> >>
> >>> iw: move to meta-networking and update
> >>
> >> This is receferenced by a packagegroup in meta-oe:
> >> meta-oe/recipes-core/packagegroups/packagegroup-basic.bb:
> >> ${@base_contains("DISTRO_FEATURES", "wifi", "iw wpa-supplicant", "", d)}
> >> \
> >>
> >>
> >> With the 'meta-oe shall only depend on oe-core' rule,
> >
> > Are you sure nothing in meta-oe depends on anything in other layers within
> > meta-openembedded already?
>
> I can't say for certain, but Martin and I have been very strict about it in
> the past. If there are such external dependencies they should be looked at
> and fixed.
At some point I don't think this is going to be realistic - what happens if
you have something in meta-oe that's too generic to be put elsewhere and yet
has a dependency on something in meta-multimedia or meta-networking? It will
come up at some point fairly soon.
I can drop the iw patch from this set for the sake of the rest of the patches
if you object to moving it, but we do need to do something about this in the
near future.
For now, I did check and at the moment according to "bitbake-layers show-
cross-depends" (thank you Robert) we have only vlc depending on fluidsynth
which is in meta-multimedia, but vlc ought to be moved to meta-multimedia
itself anyway.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-04-16 13:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 10:53 [meta-networking, meta-oe][PATCH 0/9] Move networking recipes to meta-networking Paul Eggleton
2013-04-16 10:53 ` [meta-networking, meta-oe][PATCH 1/9] vsftpd: move from meta-oe to meta-networking and tweak Paul Eggleton
2013-04-16 10:53 ` [meta-networking, meta-oe][PATCH 2/9] iw: move to meta-networking and update Paul Eggleton
2013-04-16 10:53 ` [meta-networking, meta-oe][PATCH 3/9] openvpn: move to meta-networking and tweak Paul Eggleton
2013-04-16 12:01 ` Martin Jansa
2013-04-16 10:53 ` [meta-networking, meta-oe][PATCH 4/9] bridge-utils: " Paul Eggleton
2013-04-16 10:53 ` [meta-networking, meta-oe][PATCH 5/9] rp-pppoe: move from meta-oe " Paul Eggleton
2013-04-16 10:54 ` [meta-networking, meta-oe][PATCH 6/9] dnsmasq: move " Paul Eggleton
2013-04-16 10:54 ` [meta-networking, meta-oe][PATCH 7/9] ipsec-tools: " Paul Eggleton
2013-04-16 10:54 ` [meta-networking, meta-oe][PATCH 8/9] strongswan: move to meta-networking Paul Eggleton
2013-04-16 10:54 ` [meta-networking, meta-oe][PATCH 9/9] atftp: move to meta-networking and tweak Paul Eggleton
2013-04-16 11:01 ` [meta-networking, meta-oe][PATCH 0/9] Move networking recipes to meta-networking Jack Mitchell
2013-04-16 12:30 ` Paul Eggleton
2013-04-16 12:39 ` Jack Mitchell
2013-04-16 11:09 ` Koen Kooi
2013-04-16 11:19 ` Paul Eggleton
2013-04-16 11:30 ` Koen Kooi
2013-04-16 12:11 ` Martin Jansa
2013-04-16 13:22 ` Paul Eggleton [this message]
2013-04-16 13:56 ` Martin Jansa
2013-04-29 18:01 ` Joe MacDonald
2013-04-29 18:04 ` Joe MacDonald
2013-04-29 18:45 ` Martin Jansa
2013-04-29 18:54 ` Joe MacDonald
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=2803066.5t2BvEp21p@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox