On Fri, May 6, 2011 at 1:23 PM, Jeff King <peff@xxxxxxxx> wrote: > 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html