Added a comment: Relying on path is not best practice in a Windows environment
This commit is contained in:
parent
29f13435e5
commit
940b92926f
1 changed files with 22 additions and 0 deletions
|
@ -0,0 +1,22 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="Hans_Ryding"
|
||||||
|
ip="81.229.194.7"
|
||||||
|
subject="Relying on path is not best practice in a Windows environment"
|
||||||
|
date="2014-08-25T16:16:33Z"
|
||||||
|
content="""
|
||||||
|
Unlike under POSIX environments
|
||||||
|
generally applications under windows don't add themselves to path,
|
||||||
|
or to a directory already in path.
|
||||||
|
|
||||||
|
Generally applications announce their location using the registry.
|
||||||
|
Under either HKEY_LOCAL_MACHINE\SOFTWARE,
|
||||||
|
or in case of software installed for one particular user only
|
||||||
|
under HKEY_CURRENT_USER\SOFTWARE.
|
||||||
|
|
||||||
|
Git however AFAIK does not.
|
||||||
|
Most likely the best thing to do is to prompt the user when installing git-annex
|
||||||
|
where git is, and store this variable.
|
||||||
|
|
||||||
|
Note that in both my installs I installed git-annex into the git directory,
|
||||||
|
and the git-annex webapp still couldn't find it.
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue