On Jul 10, 2008, at 9:29 PM, Johannes Sixt wrote:
On Mittwoch, 9. Juli 2008, Johannes Schindelin wrote:
Hi,
On Wed, 9 Jul 2008, Johannes Sixt wrote:
On Mittwoch, 9. Juli 2008, Johannes Schindelin wrote:
On Tue, 8 Jul 2008, Johannes Sixt wrote:
We could derive directories like this:
[*] [+]
(1) git.exe -----> exec-path -----> templates
|\----> etc/gitconfig
\----> html docs
or we could do it like this:
[*]
(2) git.exe ------> exec-path
| [+]
|\-----> templates
|\-----> etc/gitconfig
\-----> html docs
[*] can be overridden with --exec-path option or GIT_EXEC_PATH env
var [+} can be overridden with --template option
GIT_TEMPLATE_DIR env
var
Which one is more appropriate?
IMHO 2), since the templates directory and the exec-path
directory are
same in nature: they are directories with additional stuff.
With (1) you could install git.exe (or even a symlink to git on
Unix)
somewhere in $PATH, and the rest in $anywhere and just point
GIT_EXEC_PATH (and only that) to $anywhere/libexec/git-core. Would
you
think that this feature is not worth it?
Correct. I think this feature is not worth it. I think all of Git
should
be installed in one place, on Windows.
OK, I'll take that route then. It's easier to implement, I think,
and the
default settings are less cryptic: all of them are relative to $
(bindir); in
version (1) $(gitexecdir) would be relative to $(bindir), and the
others
relative to $(gitexecdir).
I've been offline the last couple of days.
I'll send patches related to htmldir that might conflict with your
planned
changes. If you haven't yet started you could have a look on the patch
that introduces system_path() before you start.
Steffen
