From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Knight <james.d.knight@live.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/util-linux: adding cfdisk enablement comment
Date: Sat, 10 Oct 2026 23:06:26 +0200 [thread overview]
Message-ID: <asqozZsoekYSa9YL@windsurf> (raw)
In-Reply-To: <CYYP221MB114065AD82DF8DF273CA6105A04C2@CYYP221MB1140.NAMP221.PROD.OUTLOOK.COM>
On Fri, Feb 16, 2024 at 12:57:57AM -0500, James Knight wrote:
> This commit introduces a menu comment to users to indicate whether the
> `cfdisk` can be built, even when the basic set binaries option is
> enabled.
>
> For users wishing to support `fdisks` utilities (cfdisk, fdisk and
> sfdisk) in Buildroot, these utilities are enabled through a
> `BR2_PACKAGE_UTIL_LINUX_BINARIES` option. This option configures
> `all-programs`, which will default enable `fdisks` (along with other
> program options that do not have an explicit configuration). While a
> user can enable "all programs", there is no guarantee that the `cfdisk`
> utility will be built if neither ncurses or slang is enabled. Even if
> an explicit Buildroot menu option is added for `cfdisk` (where we can
> force select ncurses, if slang is not yet enabled), there is no specific
> configuration option in util-linux to toggle the enablement of `cfdisk`
> at this time.
>
> Signed-off-by: James Knight <james.d.knight@live.com>
Applied to master, thanks!
Best regards,
Thomas Petazzoni
--
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
prev parent reply other threads:[~2026-10-13 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240216055757.1588-1-james.d.knight@live.com>
2024-02-16 5:57 ` [Buildroot] [PATCH 2/2] package/util-linux: adding cfdisk enablement comment James Knight
2026-10-10 21:06 ` Thomas Petazzoni via buildroot [this message]
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=asqozZsoekYSa9YL@windsurf \
--to=buildroot@buildroot.org \
--cc=james.d.knight@live.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.