Name clash with plink from ssh clone putty

[daissi]

Hi,
I am involved in Debian Med project which provide a GNU/Linux distribution for biomedical research. I am making a package of plink2 [1] for integration in official Debian repository, but as you know, there is a name clash with plink from ssh clone putty. So, to avoid the name clash with the first plink, plink2 and plink from ssh clone putty, maybe it could be useful to change the default name of the binary to plink2 or something like that.

At http://bugs.debian.org/503367 and http://bugs.debian.org/771154#25 you can read the full discussion about a name clash between one component of the frequently used ssh software putty and plink.

Best regards,
Dylan

[1] http://anonscm.debian.org/cgit/debian-med/plink2.git/

[chrchang]

PLINK 1.9 is designed for maximal backward compatibility with 1.07, so I think it's best for it to keep the same default binary name; some users do rename it to "plink2" (and I do that myself when comparing 1.07 and 1.9) but I suggest that the Debian package stick with "p-link". If it's worked for six years, it will work for one more.

The reason is that PLINK 2.0 will break backward compatibility in more ways--a major reason 1.9 exists as a separate entity is to allow 2.0 to do this--and as a result, the latter binary will be distributed with the "plink2" default name on all platforms.