Hi: On Wed, May 14, 2008 at 8:58 PM, Schuberth, Sebastian <[EMAIL PROTECTED]> wrote: > >> From: Johannes Schindelin [mailto:[EMAIL PROTECTED] >> Anyway, here it goes: Some people prefer plink.exe to >> ssh.exe. Maybe we can ship plink.exe and have an option to >> use that by default in the Git installer? >> > I can see the benefit of using plink for people who already use PuTTY, > but I do not like the idea too much to bundle the installer with an > "external" tool (which needs being watched and updated over time).
Count me in the "do not bundle" group. As a "wishing Windows was more Unix-like" user, I always install the Putty suite. > So my suggestion would be to make the installer use an existing / user > provided plink.exe. The installer should display this option, which, if > selected, displays a text field to hold the path to plink.exe. The text > field could default to any auto-detected PuTTY installation, or be empty > otherwise. +1 This is good on the advertising and customization fronts. As far as I can tell from the PuTTY source code [1], autodetecting if Plink.exe is installed or not, and where it is, is possible in an indirect way if one has used the installer version of the suite and the defaulted checkbox "Associate .PPK files with Pageant and puttygen" is selected. I also want to mention that it is popular to use the "Portable Apps" (non-registry) version of the Putty suite [2]. [1] http://svn.tartarus.org/putty/windows/putty.iss?rev=7488&view=markup [2] http://portableapps.com/apps/internet/putty_portable Best regards, Clifford Caoile
