Re: RFC: a plugin architecture for git extensions?

From: Motiejus Jakštys <desired.mta@gmail.com>
Date: Apr 27, 2011, 19:16 UTC
Message-ID: <20110427191612.GB2667@jakstys.lt>
In-Reply-To: <BANLkTikGZgEb-4jzHt+t2k__s7BMgbU9gg@mail.gmail.com>

On Thu, Apr 28, 2011 at 02:13:56AM +1000, Jon Seymour wrote:

Show 21 quoted lines

> Platform specific concerns such as building and (most) dependency
> management will be delegated to platform specific package managers.
> 
> The overriding objective is to allow a git user to install a git
> plugin called foobar with 4 words:
> 
>      git pm install foobar
> 
> given that someone, somwhere, has done the work to create a plugin
> descriptor and create an installable package of some kind for whatever
> package managers are required in order to successfully install the
> plugin on the target platform.
> 
> The same command should work whether your git platform is hosted on
> MAC OSX, cygwin, Debian, Fedora, AIX or Windows.
> 
> Where git can be used as the underlying package manager, it will be
> (for extensions which really are just source repos). If more
> sophisticated build support is required, then that will be delegated
> to a platform specific package manager via one of a small number of
> package manager adapters.

Ok, I write my "git logx", which is a single file -- git-logx.c.
Compilation steps:
    $ gcc -lz git-logx.c.

> then that will be delegated to a platform specific package manager

Which one? Say I am on debian. dpkg-buildpackage? So I would get a git-logx.deb, which I should install as root? In that case, you forgot one word:

      sudo git pm install foobar

Or I got it wrong?

Motiejus