Add remove-tool command

[rarkins]

• remove-tool foo removes all installations of tool foo
• remove-tool foo x.y.z removes installation of foo@x.y.z
  • If another version of foo is still installed then it needs to be linked instead

[viceice]

What if there are more than 2 versions installed? Which version should be linked?

[viceice]

Should it support the <TOOL>_VERSION env variable like install-tool ?

[viceice]

What if there are more than 2 versions installed? Which version should be linked?

It's much easier to simply unlink the tool. 🤔

[viceice]

//cc @nabeelsaabna @Gabriel-Ladzaretti

[viceice]

It seems it much more tricky.

I can easily remove a version, if it's not the linked one (latest installed).

If i remove a node version which is the linked one, i don't now if the linked npm or corepack is from this node install or installed by the tool after node was installed. 🤔

[nabeelsaabna]

Unlink is not good. the main idea is to delete the file and reduce vulnerabilities in the final image.

It seems it much more tricky.

I can easily remove a version, if it's not the linked one (latest installed).

If i remove a node version which is the linked one, i don't now if the linked npm or corepack is from this node install or installed by the tool after node was installed. 🤔

That does complicate things 😕
Is it only an issue for node and npm ?
python as well ?
maybe also deleting Java can break maven and/or Gradle ?

[viceice]

yes, same for python and java.

python, node and ruby based tools are dependent on the ruby version which was linked when installed. so removal of node or ruby can break npm, bundler, pip, ...

base/src/cli/tools/node/utils.ts

Line 103 in acbf091

prefix = join(prefix, nodeVersion);

base/src/cli/tools/python/utils.ts

Line 50 in acbf091

prefix = path.join(prefix, pythonVersion);