Scott Parish schrieb:
I have a situation where software for a distribution is installed into a fake "prefix" and then moved to one of several potential places to be used by users. Given that the final location isn't static, i can't depend on builtin_exec_path. I'd really like users to be able to get started with git as easily as possible. With the current setup, they would have to create and maintain either an GIT_EXEC_PATH or an alias for including --exec-path, as well as a MANPATH and PERL5LIB. This seem like an unnessisary burden.
Interesting. How does this compare to this 2-patch-series: http://repo.or.cz/w/git/mingw.git?a=commitdiff;h=e479ea2f911b8c70a269ba59372a4fef90f8907c http://repo.or.cz/w/git/mingw.git?a=commitdiff;h=00a4ff4f3f8ec7e6b3ac15456f00b22b03f438ae which I had come up with to accomplish something very similar (on Windows). Your approach looks superior, but I hadn't gone into depths, yet. -- Hannes - 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
