From: Koen Kooi <koen@dominion.thruhere.net>
To: 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 13:09:46 +0200 [thread overview]
Message-ID: <kkjbhk$h9r$1@ger.gmane.org> (raw)
In-Reply-To: <cover.1366109533.git.paul.eggleton@linux.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 16-04-13 12:53, Paul Eggleton schreef:
> This moves most of the remaining networking recipes in meta-oe to
> meta-networking, with some additional tidying up.
>
>
> The following changes since commit
> a45830a39bb47a9eab27980d52966226c9504ea4:
>
> recipes: Unify indentation (2013-04-15 16:23:17 +0200)
>
> are available in the git repository at:
>
> git://git.openembedded.org/meta-openembedded-contrib
> paule/meta-networking-moves2
> http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=paule/meta-networking-moves2
>
> Paul Eggleton (9): vsftpd: move from meta-oe to meta-networking and
> tweak openvpn: move to meta-networking and tweak bridge-utils: move to
> meta-networking and tweak rp-pppoe: move from meta-oe to meta-networking
> and tweak dnsmasq: move to meta-networking and tweak ipsec-tools: move to
> meta-networking and tweak strongswan: move to meta-networking atftp: move
> to meta-networking and tweak
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, iw can't get moved to
meta-networking. Since iw is replacing wireless-tools I think it should move
to OE-core instead.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFRbTF6MkyGM64RGpERApLoAJ9VE1iFJzYL0mXye+f+VQnukWJIqgCgtDzn
jRT3AEDi+XnA5L15qYPqkrw=
=kUrm
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-04-16 11:27 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 [this message]
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
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='kkjbhk$h9r$1@ger.gmane.org' \
--to=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 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.