From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Sinan Kaya <okaya@kernel.org>, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [meta-oe][PATCH v3] iproute2: split ip to individual package
Date: Wed, 16 Dec 2020 17:00:17 +0000 [thread overview]
Message-ID: <497c9433b74b13fc96510739deb4b41d2ea2fd5e.camel@linuxfoundation.org> (raw)
In-Reply-To: <20201216164510.9823-1-okaya@kernel.org>
On Wed, 2020-12-16 at 16:45 +0000, Sinan Kaya wrote:
> Move the ip tool into its own package. Useful for size constrained
> systems that only want the ip tool.
>
> Signed-off-by: Sinan Kaya <okaya@kernel.org>
> ---
> .../iproute2/iproute2.inc | 47 ++++++++++++++++++-
> 1 file changed, 45 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-connectivity/iproute2/iproute2.inc b/meta/recipes-connectivity/iproute2/iproute2.inc
> index 403d264308c..c7a3d547dae 100644
> --- a/meta/recipes-connectivity/iproute2/iproute2.inc
> +++ b/meta/recipes-connectivity/iproute2/iproute2.inc
> @@ -46,32 +46,75 @@ do_install () {
> # The .so files in iproute2-tc are modules, not traditional libraries
> INSANE_SKIP_${PN}-tc = "dev-so"
>
> -PACKAGES =+ "\
> +IPROUTE2_PACKAGES =+ "\
> + ${PN}-bridge \
> ${PN}-devlink \
> ${PN}-genl \
> + ${PN}-ifcfg \
> ${PN}-ifstat \
> + ${PN}-ip \
> + ${PN}-lib \
> ${PN}-lnstat \
> ${PN}-nstat \
> + ${PN}-rdma \
> + ${PN}-routef \
> + ${PN}-routel \
> + ${PN}-rtmon \
> + ${PN}-rtpr \
> ${PN}-rtacct \
> ${PN}-ss \
> ${PN}-tc \
> ${PN}-tipc \
> "
I accept there is a case for splitting out ip, the patch now splits out
every binary though? That isn't what the commit message says...
Cheers,
Richard
next prev parent reply other threads:[~2020-12-16 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 16:45 [meta-oe][PATCH v3] iproute2: split ip to individual package Sinan Kaya
2020-12-16 17:00 ` Richard Purdie [this message]
2020-12-16 17:09 ` [OE-core] " Sinan Kaya
2020-12-16 17:24 ` Richard Purdie
2020-12-16 17:25 ` Sinan Kaya
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=497c9433b74b13fc96510739deb4b41d2ea2fd5e.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=okaya@kernel.org \
--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