From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "José Luis Salvador Rufo" <salvador.joseluis@gmail.com>
Cc: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] docs/manual/prerequisite.txt: add diffutils
Date: Wed, 27 Jul 2022 00:04:02 +0200 [thread overview]
Message-ID: <20220727000402.53dff223@windsurf> (raw)
In-Reply-To: <20220426132833.1579873-1-salvador.joseluis@gmail.com>
On Tue, 26 Apr 2022 15:28:34 +0200
José Luis Salvador Rufo <salvador.joseluis@gmail.com> wrote:
> Patch title: docs/manual/prerequisite.txt: add diffutils
>
> The command `cmp` is used by `package/pkg-generic.mk` at commit
> 8623cc5deb5. This command is provided by `diffutils`.
>
> Signed-off-by: José Luis Salvador Rufo <salvador.joseluis@gmail.com>
> ---
> docs/manual/prerequisite.txt | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, thanks.
In addition to this patch we also:
1. Added a check for cmp in support/dependencies/dependencies.sh
2. Dropped the use of host-diffutils from opkg-utils
3. Dropped host-diffutils itself
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-26 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 13:28 [Buildroot] [PATCH 1/1] docs/manual/prerequisite.txt: add diffutils José Luis Salvador Rufo
2022-04-26 17:16 ` Baruch Siach via buildroot
2022-04-26 22:01 ` Thomas Petazzoni via buildroot
2022-04-27 4:34 ` Baruch Siach via buildroot
2022-04-27 6:22 ` José Luis Salvador Rufo
2022-07-26 22:04 ` Thomas Petazzoni via buildroot [this message]
2022-08-29 11:15 ` Peter Korsgaard
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=20220727000402.53dff223@windsurf \
--to=buildroot@buildroot.org \
--cc=salvador.joseluis@gmail.com \
--cc=thomas.de_schampheleire@nokia.com \
--cc=thomas.petazzoni@bootlin.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