Re: RFC: a plugin architecture for git extensions?

From: Jon Seymour <jon.seymour@gmail.com>
Date: Apr 27, 2011, 08:15 UTC
Message-ID: <BANLkTinrU8LhA0RORde0e5a1TM5VB5gVNQ@mail.gmail.com>
In-Reply-To: <4DB7CC7C.2050508@drmicha.warpmail.net>

On Wed, Apr 27, 2011 at 5:57 PM, Michael J Gruber <git@drmicha.warpmail.net> wrote:

Show 5 quoted lines

>
> I'm sorry to spoil the party before it started but I'm not very fond of
> having yet another package manager orthogonal to what distributions have
> already. This is definitely not a way to get anything like that into a
> distribution which has proper policies.

I am happy to defer work on a full-blown package manager for now. I do agree, the world already has a surfeit of package managers. As I say, I'd prefer a minimal interface that could be back-ended by one or more of those if possible.

Initially I'd like to focus on:

* a descriptor format for packages providing hints about how to
activate an extension
* guidelines for the filesystem layout of extensions themselves
* a way to locally locate extensions that might be subject to activation
* the interface between the git runtime and the activated package repository
* the interface to activate/deactivate a locally located package

I also want to avoid baking in any too many decisions about things like registries and distribution models. That can come later.

jon.