From: "Arnd Bergmann" <arnd@arndb.de>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"Julian Braha" <julianbraha@gmail.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
ljs@kernel.org, "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nsc@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] Documentation: dev-tools: add kconfirm
Date: Mon, 27 Apr 2026 21:33:55 +0200 [thread overview]
Message-ID: <607be3b2-11bc-4074-a396-39da73089b74@app.fastmail.com> (raw)
In-Reply-To: <CANiq72=nCw+zWYhvPMJiG8oOT3zpaD8eGVUgaK5rnSzAiGGjPw@mail.gmail.com>
On Mon, Apr 27, 2026, at 20:17, Miguel Ojeda wrote:
> On Mon, Apr 27, 2026 at 7:44 PM Julian Braha <julianbraha@gmail.com> wrote:
>>
>> +kconfirm also requires the Cargo package manager and an internet
>> +connection for compilation of its dependencies.
>
> This will be quite surprising -- I think any `make` call should avoid
> touching the network and should allow working while offline as long as
> one has set up things beforehand.
>
> i.e. I think tools and dependencies in general should be fetched
> and/or installed beforehand, and then yes, `make` may use them,
> without touching the network (e.g. passing `--offline` or `--frozen`).
It would also be helpful to reduce the number of hard dependencies
and ideally only rely on packages that are already shipping in common
distros.
From the dependency list, it appears that the majority of dependencies
here are only indirectly pulled in by 'reqwest'. I guess is only
required for dead-link checking, so maybe that part could be
made optional?
Arnd
next prev parent reply other threads:[~2026-04-27 19:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 17:44 [RFC PATCH 0/2] scripts: add kconfirm Julian Braha
2026-04-27 17:44 ` [RFC PATCH 1/2] " Julian Braha
2026-04-27 20:48 ` Greg KH
2026-04-28 21:17 ` Julian Braha
2026-04-28 7:01 ` Jonathan Corbet
2026-04-28 18:31 ` Nathan Chancellor
2026-04-28 19:08 ` Jonathan Corbet
2026-04-27 17:44 ` [RFC PATCH 2/2] Documentation: dev-tools: " Julian Braha
2026-04-27 18:17 ` Miguel Ojeda
2026-04-27 19:33 ` Arnd Bergmann [this message]
2026-04-28 11:51 ` Miguel Ojeda
2026-04-28 12:58 ` Gary Guo
2026-04-28 18:45 ` Nathan Chancellor
2026-04-29 0:38 ` Miguel Ojeda
2026-04-28 17:01 ` Julian Braha
2026-04-28 8:23 ` Jani Nikula
2026-04-28 18:06 ` 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=607be3b2-11bc-4074-a396-39da73089b74@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=julianbraha@gmail.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=miguel.ojeda.sandonis@gmail.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--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