From: Adrian Bunk <bunk@stusta.de>
To: Tom Rini <trini@konsulko.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] Introduce packagegroup-core-base-utils
Date: Sat, 2 Mar 2019 09:11:40 +0200 [thread overview]
Message-ID: <20190302071140.GA2151@localhost> (raw)
In-Reply-To: <1551479212-28944-1-git-send-email-trini@konsulko.com>
On Fri, Mar 01, 2019 at 05:26:48PM -0500, Tom Rini wrote:
>...
> - busybox provides "nslookup" which at this point in time is an
> anachronism. bind stopped shipping "nslookup" prior to oe-core replacing
> the old monolithic layer. We do provide host and dig and such via
> bind-utils.
>...
I'd say this is a bug in bind-utils.
nslookup was was at some point deprecated by bind upstream,
but it was undeprecated 15 years ago.
> Tom
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-03-02 7:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 22:26 [PATCH 0/4] Introduce packagegroup-core-base-utils Tom Rini
2019-03-01 22:26 ` [PATCH 1/4] vim: Import version 8.1.0347 Tom Rini
2019-03-02 9:15 ` Martin Jansa
2019-03-02 12:36 ` Tom Rini
2019-03-02 12:57 ` Tom Rini
2019-03-02 15:42 ` Joshua Watt
2019-03-01 22:26 ` [PATCH 2/4] inetutils: Import version 1.9.4 Tom Rini
2019-03-02 17:00 ` Richard Purdie
2019-03-02 17:46 ` Tom Rini
2019-03-02 19:25 ` Richard Purdie
2019-03-02 19:28 ` Tom Rini
2019-03-04 9:47 ` André Draszik
2019-03-04 16:40 ` Tom Rini
2019-03-01 22:26 ` [PATCH 3/4] packagegroup-core-base-utils: Introduce new base-utils packagegroup Tom Rini
2019-03-02 14:41 ` Tom Rini
2019-03-04 16:44 ` Mark Hatle
2019-03-04 18:02 ` Tom Rini
2019-03-01 22:26 ` [PATCH 4/4] imagefeatures: Add test to blacklist building busybox Tom Rini
2019-03-02 7:11 ` Adrian Bunk [this message]
2019-03-02 12:36 ` [PATCH 0/4] Introduce packagegroup-core-base-utils Tom Rini
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=20190302071140.GA2151@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=trini@konsulko.com \
/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