Re: RFC: a plugin architecture for git extensions?
- From
John Szakmeister <john@szakmeister.net>
- Date
- May 7, 2011, 08:24 UTC
- Message-ID
- <BANLkTi=DreFEHWf0Ndd-3cAiaCtFgZHe2A@mail.gmail.com>
- In-Reply-To
- <20110506172334.GB16576@sigill.intra.peff.net>
On Fri, May 6, 2011 at 1:23 PM, Jeff King <peff@peff.net> wrote:
Show 22 quoted lines
> On Sat, May 07, 2011 at 12:07:14AM +1000, Jon Seymour wrote: > >> I think the problem we are trying to solve is this: how to make it as >> easy as possible to install, and get operational, an extension to git. >> >> If git supported the concept of a standard place to put extensions, >> then it could be as simple as: >> >> unzip -d $(git --plugins-dir) plugin.zip >> >> with no need to configure or choose a prefix and no need to edit the >> an .profile or .bashrc to permanently add a directory to the PATH. > > This seems slightly backwards to me. You are asking git "where should > plugins go?" and then putting them there. But that leaves no room for > plugins going in _multiple_ places. IOW, the usual hierarchy of: > > 1. distribution-packaged extensions (in /usr/share/git/plugins) > > 2. local system-wide extensions (in /usr/local/share/git/plugins) > > 3. per-user extensions (in $HOME/.gitplugins)
Exactly! I'd really like to see (3) and stop cluttering up my ~/.local/bin folder with wrapper scripts.
-John