Please describe the problem.
I had "fun" today doing some initial configuration of a laptop with Windows 10. I remembered that I need to install Git first, so did that first, 64 bit since that is what is the laptop is. Then when got to install git-annex remembered that it is recommended to install 32bit built of Git instead. Oh well, I left a comment and proceeded hoping to resolve rsync issue if/when arises. The problem came upon reboot when I got "Windows Script Host" error "Can not find script file C:\Program Files (x86)\Git\cmd\git-annex-autostart.vbs". Oh well, indeed -- there is no " (x86)\Git" and as described above it was "on purpose". So it feels that some "recommended" value is hard-coded somewhere?
P.S. I really hope that someone eventually takes time to make git-annex become available for Windows from conda-forge.
Made the NSIS gitInstallDir probe which of PROGRAMFILES/Git and PROGRAMFILES/Git exists, and use whichever. done --Joey
This is not making much sense to me, and the fact that the link to the comment that presumably provides some context is broken does not help much.
The windows installation instructions are clear that only the 32 bit build of git for windows is supported. I don't see much benefit of chasing down some way that the windows installer messes up when not following the instructions..
oops -- forgot indeed to add the actual link - fixed now.
Windows installation instructions say actually nothing about what is "supported" at all. What they say is "If you installed the 64 bit version of git, then parts of git-annex will still run, however, some features, including tools like rsync, will not work." So here was I -- exploring uncharted territories by installing git-annex to see what parts will run and which wouldn't. As I found no other report of the issue I have ran into -- I have filed a new issue instead of staying silent. If you feel that it is something you wouldn't be interested to fix ATM -- I can live with that. But at least others who run into a similar case could find this report, and I guess it would get fixed when that roadblock with rsync gets resolved.
Cheers!