From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking] [PATCH] iw: migrate from meta-oe into meta-networking and uprev to iw 3.6
Date: Wed, 26 Sep 2012 09:30:53 +0200 [thread overview]
Message-ID: <k3uava$evl$2@ger.gmane.org> (raw)
In-Reply-To: <1348631053-21801-1-git-send-email-jackie.huang@windriver.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 26-09-12 05:44, jackie.huang@windriver.com schreef:
> From: Jackie Huang <jackie.huang@windriver.com>
Most importantly: iw can't be moved out of meta-oe since packagegroup-basic
depends on it. Since iw is replacing wireless-tools it is a candidate for
oe-core.
>
> Signed-off-by: Jackie Huang <jackie.huang@windriver.com> ---
> ....sh-don-t-use-git-describe-for-versioning.patch | 44
> ++++++++++++++++++++ meta-networking/recipes-support/iw/iw_3.2.bb |
> 22 ++++++++++ meta-networking/recipes-support/iw/iw_3.6.bb | 27
> ++++++++++++
Why 2 versions?
> +++ b/meta-networking/recipes-support/iw/iw_3.6.bb @@ -0,0 +1,27 @@
> +SUMMARY = "nl80211 based CLI configuration utility for wireless
> devices" +DESCRIPTION = "iw is a new nl80211 based CLI configuration
> utility for \ +wireless devices. It supports almost all new drivers that
> have been added \ +to the kernel recently. " +HOMEPAGE =
> "http://linuxwireless.org/en/users/Documentation/iw" +SECTION = "base"
> +LICENSE = "BSD" +LIC_FILES_CHKSUM =
> "file://COPYING;md5=878618a5c4af25e9b93ef0be1a93f774" + +PR = "r0"
Remove that.
> + +DEPENDS = "libnl pkgconfig" + +SRC_URI =
> "http://wireless.kernel.org/download/iw/${P}.tar.bz2 \ +
> file://0001-iw-version.sh-don-t-use-git-describe-for-versioning.patch \ +
> " + +SRC_URI[md5sum] = "1c18bfbbc8773629e5e8ac733a39540c"
> +SRC_URI[sha256sum] =
> "df11036ac11df31f44083da962a6e9c74bdea7c01c596c4b5840f948cdb6c857" + +#
> EXTRA_OEMAKE is typically: -e MAKEFLAGS= +# the -e causes problems as
> CFLAGS is modified in the Makefile. +EXTRA_OEMAKE = ""
Same comment as with ptpd. The older version don't seem to need this hack.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFQYq8tMkyGM64RGpERAigGAJwImQk5QRWnjicqP2SgCAclj8YKTgCgsblY
ccuKk2jnfr2i3XpWBpQAn+c=
=oaSE
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-09-26 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 3:44 [meta-networking] [PATCH] iw: migrate from meta-oe into meta-networking and uprev to iw 3.6 jackie.huang
2012-09-26 7:30 ` Koen Kooi [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-26 4:09 jackie.huang
2012-09-26 4:13 jackie.huang
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='k3uava$evl$2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox