From: "René Scharfe" <l.s.r@web•de>
To: Junio C Hamano <gitster@pobox•com>, Git List <git@vger•kernel.org>
Cc: "brian m. carlson" <sandals@crustytoothpaste•net>,
Koji Nakamaru <koji.nakamaru@gree•net>
Subject: Re: [PATCH] config.mak.uname: use iconv from Homebrew on macOS
Date: Thu, 11 Dec 2025 15:34:00 +0100 [thread overview]
Message-ID: <5308d067-6c3c-4694-a30d-86a561704e6c@web.de> (raw)
In-Reply-To: <xmqqfr9he3v7.fsf@gitster.g>
On 12/11/25 10:59 AM, Junio C Hamano wrote:
>
> Does anybody know if a purely vanilla installation of macOS, without
> any third-party software collection like homebrewk, is supposed to
> be even serviceable? That is, if somebody at Apple builds a version
> of Git that they ship themselves (they do, don't they?), can they
> untar the latest tarball on a vanilla macOS box, type "make test",
> and expect it to pass?
It seems so. https://opensource.apple.com/releases/ points to
https://github.com/apple-oss-distributions/Git. The latest tag is close
to v2.50.1:
$ git diff --stat -w v2.50.1 Git-155:src/git ':(exclude)*.git*'
Documentation/fsck-msgids.adoc | 12 ------------
Makefile | 1 +
attr.c | 11 +++++++++++
builtin/help.c | 3 +--
config.c | 13 +++++++++++++
config.h | 3 +++
generate-python.sh | 2 ++
git-mergetool--lib.sh | 6 ++++--
git-svn.perl | 30 ++++++++++++++++++++++++++++++
http.c | 2 ++
perl/header_templates/runtime_prefix.template.pl | 25 +++++++++++++++++++++++++
sha1collisiondetection | 1 -
t/t4014-format-patch.sh | 3 +--
t/test-lib.sh | 3 +++
usage.c | 20 ++++++++++++++++++++
15 files changed, 116 insertions(+), 19 deletions(-)
Their top-level Makefile sets NO_GETTEXT, NO_FINK and NO_DARWIN_PORTS.
René
next prev parent reply other threads:[~2025-12-11 14:34 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 22:59 t3900 failure on macOS, iconv(3) broken? René Scharfe
2025-12-09 3:18 ` Koji Nakamaru
2025-12-09 3:50 ` Yee Cheng Chin
2025-12-09 4:03 ` Collin Funk
2025-12-09 16:33 ` Torsten Bögershausen
2025-12-09 19:35 ` René Scharfe
2025-12-09 21:24 ` Torsten Bögershausen
2025-12-09 22:25 ` René Scharfe
2025-12-09 19:35 ` [PATCH] config.mak.uname: use iconv from Homebrew on macOS René Scharfe
2025-12-09 20:39 ` Yee Cheng Chin
2025-12-09 21:27 ` René Scharfe
2025-12-10 11:17 ` Carlo Marcelo Arenas Belón
2025-12-10 17:56 ` René Scharfe
2025-12-11 2:53 ` Junio C Hamano
2025-12-11 11:17 ` Carlo Marcelo Arenas Belón
2025-12-12 2:20 ` Junio C Hamano
2025-12-12 9:16 ` René Scharfe
2025-12-12 10:02 ` Carlo Marcelo Arenas Belón
2025-12-12 13:04 ` Re* " Junio C Hamano
2025-12-12 13:48 ` René Scharfe
2025-12-12 23:39 ` Junio C Hamano
2025-12-10 16:42 ` Torsten Bögershausen
2025-12-10 17:56 ` René Scharfe
2025-12-10 23:10 ` brian m. carlson
2025-12-11 2:36 ` Junio C Hamano
2025-12-11 9:59 ` Junio C Hamano
2025-12-11 14:34 ` René Scharfe [this message]
2025-12-12 3:35 ` Junio C Hamano
2025-12-12 10:40 ` t3900 failure on macOS, iconv(3) broken? René Scharfe
2025-12-13 18:42 ` [PATCH v2 1/2] Makefile: add NO_HOMEBREW René Scharfe
2025-12-14 6:45 ` Torsten Bögershausen
2025-12-14 7:13 ` Junio C Hamano
2025-12-14 9:02 ` Torsten Bögershausen
2025-12-14 11:07 ` Junio C Hamano
2025-12-14 11:13 ` René Scharfe
2025-12-14 23:19 ` Junio C Hamano
2025-12-16 18:53 ` René Scharfe
2025-12-13 18:42 ` [PATCH v2 2/2] config.mak.uname: use iconv from Homebrew on macOS René Scharfe
2025-12-16 18:53 ` [PATCH v3 1/2] macOS: make Homebrew use configurable René Scharfe
2025-12-16 19:11 ` René Scharfe
2025-12-16 21:49 ` Torsten Bögershausen
2025-12-16 18:53 ` [PATCH v3 2/2] macOS: use iconv from Homebrew if present René Scharfe
2025-12-24 7:52 ` [PATCH v4 0/2] macOS: use iconv from Homebrew if needed and present René Scharfe
2025-12-24 8:02 ` [PATCH v4 1/2] macOS: make Homebrew use configurable René Scharfe
2025-12-24 8:03 ` [PATCH v4 2/2] macOS: use iconv from Homebrew if needed and present René Scharfe
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=5308d067-6c3c-4694-a30d-86a561704e6c@web.de \
--to=l.s.r@web$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=koji.nakamaru@gree$(echo .)net \
--cc=sandals@crustytoothpaste$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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