Re: [RFD] Libification proposal: separate internal and external interfaces

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 8, 2024, 21:29 UTC
Message-ID: <xmqqr0ff8rwo.fsf@gitster.g>
In-Reply-To: <ZhND3hZXlzDxff5e@tapette.crustytoothpaste.net>

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

Show 6 quoted lines

> As mentioned in the original proposal, we don't have to support all
> platforms in the libified code.  The main Git binaries will continue to
> function and be supported, but the new libified code will rely on newer
> features.  You will still be able to have all the Git binaries and
> functionality, but if you want the new shared library to compile
> against, you'll have to furnish a newer compiler.

I thought one of the yardstick to gauge the success of this "libification" effort, if not the purpose of this effort, is to allow Git to be its first client.

I am not sure how it would supposed to work. Unless you are giving parallel implementations of "main Git binaries", one with the native code and the other replaced the native code with thin wrappers around the library calls, that is.

Puzzled...