On Fri, 29 Apr 2011, Jon Seymour wrote:
However, let's start simple, what would a minimal plugin directory
look like and, assuming there was one per git-install, where would it
be located relative to the prefix?
Here's a suggestion for the layout:
bin/
- all scripts and sh libraries
man/
- all man pages
html/
- all html pages
What about location?
${prefix}/git-plugins
${prefix}/lib/git-plugins
Or, decided by distribution?
distros are going to change this anyway, so start by accepting that, then
make the default just that, a default, not something hard-coded.
Is there support for the idea of adding a --man-path switch to the main line?
What about a --plugins-path, that would answer the question about
where plugins should go?
I think it would be better to put it in the config file, nobody is going
to add command line options to every command they run.
Per Jonathan's and Junio's suggestions, the idea of having a plugins
search path seems like a reasonable one, so that users without control
over the git install can at least customize it themselves.
only if you make sure that the plugins only run as the user, with no
chance of them being invoked as a privilaged user.
David Lang
How would this path be configured by the user? Would the user
configuration edit the git default or would it override it?
If there are multiple plugin directories, how would a plugin discover
which one it has been installed in so that it can find any
plugin-specific resource it might need?
Regards,
jon.
--
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
--
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