From: Julian Braha <julianbraha@gmail.com>
To: Demi Marie Obenour <demiobenour@gmail.com>,
nathan@kernel.org, nsc@kernel.org
Cc: jani.nikula@linux.intel.com, akpm@linux-foundation.org,
gary@garyguo.net, ljs@kernel.org, arnd@arndb.de,
gregkh@linuxfoundation.org, masahiroy@kernel.org,
ojeda@kernel.org, corbet@lwn.net, qingfang.deng@linux.dev,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [RFC v2 0/2] add kconfirm
Date: Wed, 13 May 2026 14:59:35 +0100 [thread overview]
Message-ID: <bc46423d-54aa-4773-bcad-e1c125086812@gmail.com> (raw)
In-Reply-To: <8fe7c7c8-00f7-4a72-a984-e929f71bec22@gmail.com>
On 5/11/26 05:24, Demi Marie Obenour wrote:
> This adds too many dependencies.
>
> Some suggestions:
>
> - Use system libcurl instead of ureq.
> - Use libc getopt_long instead of clap.
> - Use manual FFI bindings instead of third-party crates.
> - Use the C Kconfig parser instead of a third-party library.
Hi Demi, thanks for going in-depth on the alternatives.
Unfortunately, given the amount of analysis performed on the parse tree,
even just replacing the parser amounts to a wholesale rewrite of the
tool.
I will look into the others though, just to reduce the amount of trust
that kconfirm users need to invest in the Rust ecosystem.
- Julian Braha
next prev parent reply other threads:[~2026-05-13 13:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 20:38 [RFC v2 0/2] add kconfirm Julian Braha
2026-05-09 20:38 ` [RFC PATCH v2 1/2] scripts: " Julian Braha
2026-05-11 9:57 ` Jani Nikula
2026-05-11 13:18 ` Julian Braha
2026-05-09 20:38 ` [RFC PATCH v2 2/2] Documentation: dev-tools: " Julian Braha
2026-05-10 5:06 ` [RFC v2 0/2] " Jan Engelhardt
2026-05-10 9:49 ` Miguel Ojeda
2026-05-10 23:06 ` Julian Braha
2026-05-13 14:12 ` Julian Braha
2026-05-10 23:28 ` Jan Engelhardt
2026-05-13 15:52 ` Miguel Ojeda
2026-05-11 4:24 ` Demi Marie Obenour
2026-05-13 13:59 ` Julian Braha [this message]
2026-05-13 15:22 ` Nicolas Schier
2026-05-13 16:04 ` Julian Braha
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=bc46423d-54aa-4773-bcad-e1c125086812@gmail.com \
--to=julianbraha@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=demiobenour@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--cc=qingfang.deng@linux.dev \
--cc=rust-for-linux@vger.kernel.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