Check if the cli tool already exists

[ahaoboy]

I installed fnm to ~/tool/fnm using the official fnm installation script

Then use cargo binstalll fnm to install fnm to ~/.cargo/fnm

This results in two copies of fnm, and ~/tool has a higher priority than ~/.cargo in the system path.

When I use cargo binstall fnm to install the latest version again, although the latest version is installed to ~/.cargo, the old version is still used in shell

Is it possible to add a detection that if the installed program already exists and is not in ~/.cargo, the user should be prompted that this may be a risk?

[NobodyXu]

Hmmm yes it'd be possible, since we have the BinFile we can just try locating them, but there could be a program with the same name

We can also try executing it and checking status, but some program might fail when no cmdline argument is passed.

We could use checksum but if it's different version then it's no good.

My opinion is that it's possible but it would not be perfect and there will be false positives and false negatives, it can only serve as a hint and user has to manually verify.

[NobodyXu]

Hmmm yes it'd be possible, since we have the BinFile we can just try locating them, but there could be a program with the same name

We can also try executing it and checking status, but some program might fail when no cmdline argument is passed.

We could use checksum but if it's different version then it's no good.

My opinion is that it's possible but it would not be perfect and there will be false positives and false negatives, it can only serve as a hint and user has to manually verify.

[ahaoboy]

My opinion is that it's possible but it would not be perfect and there will be false positives and false negatives, it can only serve as a hint and user has to manually verify.

It doesn't need to be perfect, and it doesn't need to check the version, just a warning prompt is enough.