Re: RFC: a plugin architecture for git extensions?

[Pau Garcia i Quiles <pgquiles@elpauer.org>]

On Thu, Apr 28, 2011 at 10:09 AM, Jon Seymour <jon.seymour@gmail.com> wrote:

> Ok, I have tried to explain why separating the concerns of package
> management and plugin management is an appropriate thing to do, and
> why one directory for each plugin is also a good thing to do. BTW: I
> thought you actually suggested this concept yourself in your earlier
> post.

Please, re-read my mails. I *am* suggesting that plugins store data in
different directories!

- The "main command" (git-atomic, for instance) would be stored in
GIT_PREFIX/lib/git-plugins (instead of GIT_PREFIX/lib/git-core, which
is where git stores its commands). Git would have to learn to search
in GIT_PREFIX/lib/git-plugins in addition to git-core, of course.

- Porcelain for git-atomic would go to
GIT_PREFIX/lib/git-plugins/git-atomic (or something like this)

- The documentation would be stored in GIT_PREFIX/doc/git-atomic

- Resources in GIT_PREFIX/share/git-atomic

- etc

I. e. each plugin stores its stuff in a separate directory, it's just
that directory is not a *single* directory but *many* directories,
each one inside the proper path under GIT_PREFIX, just like it is for
anything you install on a Unix system

-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)