Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Nicolas Boichat via buildroot <buildroot@buildroot.org>
Cc: Nicolas Boichat <drinkcat@google.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/screenfetch: Add mawk/gawk dependency, and upstream detection patch.
Date: Sun, 6 Aug 2023 15:33:08 +0200	[thread overview]
Message-ID: <20230806153308.4c0cf791@windsurf> (raw)
In-Reply-To: <20230806121729.3552502-1-drinkcat@google.com>

Hello Nicolas,

On Sun,  6 Aug 2023 12:17:29 +0000
Nicolas Boichat via buildroot <buildroot@buildroot.org> wrote:

> screenfetch requires an "awk" implementation: add that to dependencies.
> 
> Also, upstream would only use an executable called "awk": pick up
> upstream patch that can autodetect awk implementation, so that
> "mawk" can be used.
> 
> Signed-off-by: Nicolas Boichat <drinkcat@google.com>

Thanks for the patch. One question below.

> diff --git a/package/screenfetch/Config.in b/package/screenfetch/Config.in
> index c0e7100f38..00248bafcf 100644
> --- a/package/screenfetch/Config.in
> +++ b/package/screenfetch/Config.in
> @@ -2,8 +2,12 @@ config BR2_PACKAGE_SCREENFETCH
>  	bool "screenfetch"
>  	depends on BR2_USE_MMU # bash
>  	depends on BR2_PACKAGE_BUSYBOX_SHOW_OTHERS # bash
> +	depends on BR2_PACKAGE_GAWK || BR2_PACKAGE_MAWK # runtime dependency

Would the "awk" implementation from Busybox also work? It's the awk
implementation that we use by default.

Also, just like bash is enabled via "select", we should if possible try
to do the same for the awk implementation. I don't know if something like:

	select BR2_PACKAGE_BUSYBOX if !BR2_PACKAGE_GAWK || !BR2_PACKAGE_MAWK

would work (of course, assuming the "awk" from Busybox is good enough).

Thanks for your feedback,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-08-06 13:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-06 12:17 [Buildroot] [PATCH 1/1] package/screenfetch: Add mawk/gawk dependency, and upstream detection patch Nicolas Boichat via buildroot
2023-08-06 13:33 ` Thomas Petazzoni via buildroot [this message]
2023-08-07  8:22   ` Nicolas Boichat via buildroot
2023-08-11 20:18     ` Arnout Vandecappelle via buildroot
2023-08-11 22:27       ` Thomas Petazzoni via buildroot
2023-08-12  1:01         ` Nicolas Boichat via buildroot

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=20230806153308.4c0cf791@windsurf \
    --to=buildroot@buildroot.org \
    --cc=drinkcat@google.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