Re: Proposal/Discussion: Turning parts of Git into libraries

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Mar 23, 2023, 23:37 UTC
Message-ID: <CAMP44s2AMrXCN6f6v-W0sqb++TVfHf7Q1miJE7iZjZOVwFQa0Q@mail.gmail.com>
In-Reply-To: <CAJoAoZ=Cig_kLocxKGax31sU7Xe4==BGzC__Bg2_pr7krNq6MA@mail.gmail.com>

On Fri, Feb 17, 2023 at 3:45 PM Emily Shaffer <nasamuffin@google.com> wrote:

Show 10 quoted lines

> As I mentioned in standup this week[1], my colleagues and I at Google
> have become very interested in converting parts of Git into libraries
> usable by external programs. In other words, for some modules which
> already have clear boundaries inside of Git - like config.[ch],
> strbuf.[ch], etc. - we want to remove some implicit dependencies, like
> references to globals, and make explicit other dependencies, like
> references to other modules within Git. Eventually, we'd like both for
> an external program to use Git libraries within its own process, and
> for Git to be given an alternative implementation of a library it uses
> internally (like a plugin at runtime).

This is obviously the way it should have been done from the beginning, but unfortunately at this point the Git project has too much inertia and too many vested interests from multi-billion dollar corporations to change.

I wonder if a single person who isn't paid to work on Git commented on this thread.

I don't think these kinds of laudable efforts can be achieved within the Git project.

Cheers.

-- 
Felipe Contreras