Re: RFC: a plugin architecture for git extensions?
- From
Jon Seymour <jon.seymour@gmail.com>
- Date
- May 6, 2011, 14:29 UTC
- Message-ID
- <BANLkTikW2u2W=Hpw2G4VJf_h88x4_7x_=Q@mail.gmail.com>
- In-Reply-To
- <20110506141719.GA2991@elie>
On Sat, May 7, 2011 at 12:17 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 14 quoted lines
> Jon Seymour wrote: > >> 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. > > Why not use "/usr/local" in place of "git --plugins-dir"? (I can > think of one answer --- namely root privileges --- but it would apply > to any system with one standard place to put extensions.) >
Partly because that is second guessing &/or reverse engineering the distribution's decisions and it won't work for a Windows install where there is no /usr/local
Not that I currently, have a need, but Junio did mention the case where someone wants to enhance an existing git command with a wrapper of some kind. This could be done more precisely if git itself controlled the relative order of the path components than if one relied on /usr/local being in a particular place in the path.
jon.