From: Jeff King <peff@peff.net>
To: M Hickford <mirth.hickford@gmail.com>
Cc: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>,
"Taylor Blau" <me@ttaylorr.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Which macOS versions does Git support?
Date: Mon, 22 May 2023 15:24:37 -0400 [thread overview]
Message-ID: <20230522192437.GB365027@coredump.intra.peff.net> (raw)
In-Reply-To: <CAGJzqsmJSVJYTtT41wQ5Cgsz=ExMZ8y7qKPDh-7kt8RXY__NbQ@mail.gmail.com>
On Sat, May 20, 2023 at 08:36:58AM +0100, M Hickford wrote:
> > FWIW Mac OS X 10.5 (Leopard) was last updated in 2009 and also happens to
> > be the last one that can run in PowerPC, so sadly there is a non zero
> > number of users for it (MacPorts uses a minimum of 10.4 for that reason)
>
> Interesting! https://ports.macports.org/port/git/details/ It looks
> like the most recent build is from 2021
> https://ports.macports.org/port/git/builds/?builder_name__name=10.5_ppc_legacy
> . https://ports.macports.org/port/git/stats/?days=365&days_ago=0
> shows 10 total PowerPC downloads in the past year between versions
> 10.4, 10.5 and 10.6
One nice thing here is that the credential helpers are pretty
independent from the rest of Git. If new versions of the helper drop
support for the old API, people on ancient systems can still use the old
helper. We'd just have to make a decision about how much to help them:
1. (least help) Tell them to dig it out of git.git history, build, and
stuff the resulting binary somewhere.
2. (most help) Support both, selected by an #ifdef and a Makefile
knob, and maybe even turn the knob automatically based on "uname
-r".
3. (middle ground) Rewrite with the new API, but leave the old helper
as contrib/osxkeychain-old or something. Still easy-ish to build,
but carries less maintenance burden.
> I don't have the equipment or expertise to develop on macOS, so I'll
> leave the API migration as a potential future #leftoverbits
I'd probably do (3), but as I also lack equipment or expertise, I'm not
planning on working on it myself (and I'd let whoever does decide to do
that work have the final say on approach).
> Reading the keychain docs more carefully, the new API only supports a
> fixed set of attribute keys such as 'kSecAttrComment', so discount my
> original "further motivation"
Bummer. Thanks for looking into this, though.
-Peff
prev parent reply other threads:[~2023-05-22 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 7:00 Which macOS versions does Git support? M Hickford
2023-05-19 9:09 ` Jeff King
2023-05-19 17:49 ` Jeff Hostetler
2023-05-20 0:37 ` Carlo Marcelo Arenas Belón
2023-05-20 7:36 ` M Hickford
2023-05-22 19:24 ` Jeff King [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=20230522192437.GB365027@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=carenas@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=mirth.hickford@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).