From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Patrick Steinhardt <ps@pks.im>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Karthik Nayak <karthik.188@gmail.com>
Subject: Re: [PATCH v2 0/4] gitlab-ci: fix the cargo invocation in the Windows job
Date: Mon, 28 Sep 2026 15:41:39 +0200 (CEST) [thread overview]
Message-ID: <139c09f8-a126-c24f-9264-154f9b2e38bd@gmx.de> (raw)
In-Reply-To: <aroOHoSXsemSlP-7@pks.im>
[-- Attachment #1: Type: text/plain, Size: 2175 bytes --]
Hi Patrick,
On Mon, 28 Sep 2026, Patrick Steinhardt wrote:
> On Thu, Sep 24, 2026 at 08:01:49PM +0000, Johannes Schindelin via GitGitGadget wrote:
> > Range-diff vs v1:
> >
> > 1: 6a389b2bad ! 1: cdf2eff480 ci(gitlab,windows): provision GNU Rust for SDK-based MinGW builds
> > @@ Metadata
> > ## Commit message ##
> > ci(gitlab,windows): provision GNU Rust for SDK-based MinGW builds
> >
> > - The minimal Git for Windows SDK already supplies Git and GCC. The
> > - MinGW Makefile build needs the GNU Rust toolchain, not another Git
> > - installation or Meson.
> > + The minimal Git for Windows SDK already supplies Git and GCC. The MinGW
> > + Makefile build needs the Rust toolchain that targets GCC (as opposed to
> > + the more common MSVC one), not another Git installation or Meson.
>
> By the way, are there plans to eventually include Rust as part of the
> GfW SDK? Just asking out of curiosity.
I'm still agonizing over that. There is now this new `sha1dc` Rust crate I
want to integrate (patch series about to land), therefore I need to get
going with including Rust in Git for Windows' SDK. But it's not looking so
rosy! As described in the PR to include Rust in Git for Windows at
https://github.com/git-for-windows/git-sdk-64/pull/132, the addition comes
at the price of roughly 110MB.
Given that `git-sdk-x86_75-minimal.tar.zst` weighs just under 70MB (see
https://github.com/git-for-windows/git-sdk-64/releases/ci-artifacts), that
would more than _double_ its size!
So I'm really torn between including Rust (and having a strict subset of
the same setup in CI as is used to build Git for Windows releases) or
alternatively stick with the current strategy: Expect the correct Rust
toolchain to be installed separately in CI.
On GitHub Actions, Rust is basically already there, and we'd save a 110MB
extra download for _ever_ `win-*` job (of which there are _a lot_ on any
given day).
But GitLab runners do not (yet?) come with Rust preinstalled, so... 🤷
> Overall I'm happy with this version, thanks!
Thanks!
Johannes
next prev parent reply other threads:[~2026-09-28 13:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 12:12 [PATCH 0/4] gitlab-ci: fix the cargo invocation in the Windows job Johannes Schindelin via GitGitGadget
2026-09-19 12:12 ` [PATCH 1/4] ci(gitlab,windows): provision GNU Rust for SDK-based MinGW builds Johannes Schindelin via GitGitGadget
2026-09-24 11:21 ` Patrick Steinhardt
2026-09-24 19:26 ` Johannes Schindelin
2026-09-19 12:12 ` [PATCH 2/4] ci(gitlab,windows): preserve exclusions during dependency setup Johannes Schindelin via GitGitGadget
2026-09-24 11:21 ` Patrick Steinhardt
2026-09-19 12:12 ` [PATCH 3/4] ci(gitlab,windows): fix Rust setup for GitLab's MinGW build Johannes Schindelin via GitGitGadget
2026-09-24 11:22 ` Patrick Steinhardt
2026-09-24 19:55 ` Johannes Schindelin
2026-09-28 6:50 ` Patrick Steinhardt
2026-09-28 14:33 ` Junio C Hamano
2026-09-19 12:12 ` [PATCH 4/4] ci(gitlab,windows): provide GNU Rust's host-linker support Johannes Schindelin via GitGitGadget
2026-09-24 11:22 ` Patrick Steinhardt
2026-09-24 19:57 ` Johannes Schindelin
2026-09-19 13:37 ` [PATCH 0/4] gitlab-ci: fix the cargo invocation in the Windows job Karthik Nayak
2026-09-20 15:27 ` Johannes Schindelin
2026-09-21 14:03 ` Karthik Nayak
2026-09-22 11:50 ` Johannes Schindelin
2026-09-23 12:43 ` Karthik Nayak
2026-09-24 20:01 ` [PATCH v2 " Johannes Schindelin via GitGitGadget
2026-09-24 20:01 ` [PATCH v2 1/4] ci(gitlab,windows): provision GNU Rust for SDK-based MinGW builds Johannes Schindelin via GitGitGadget
2026-09-24 20:01 ` [PATCH v2 2/4] ci(gitlab,windows): preserve exclusions during dependency setup Johannes Schindelin via GitGitGadget
2026-09-24 20:01 ` [PATCH v2 3/4] ci(gitlab,windows): fix Rust setup for GitLab's MinGW build Johannes Schindelin via GitGitGadget
2026-09-24 20:01 ` [PATCH v2 4/4] ci(gitlab,windows): provide GNU Rust's host-linker support Johannes Schindelin via GitGitGadget
2026-09-28 6:50 ` [PATCH v2 0/4] gitlab-ci: fix the cargo invocation in the Windows job Patrick Steinhardt
2026-09-28 13:41 ` Johannes Schindelin [this message]
2026-09-28 14:26 ` Junio C Hamano
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=139c09f8-a126-c24f-9264-154f9b2e38bd@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=karthik.188@gmail.com \
--cc=ps@pks.im \
/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