Skip to content

gdk update / asdf plugins

Overview

For many years I've used rvm to install my ruby environments. Recently I switched to asdf to see how well it worked. I installed only the ruby plugin to asdf.

Imagine my surprise when a few days later I noticed:

$ asdf plugin list
golang
minio
nodejs
postgres
redis
ruby
yarn

Oh my. This is causing havoc on my system. I already have golang setup on my computer via Homebrew. I already have nodejs and yarn via Homebrew as well. But now:

$ which yarn
/Users/atroschinetz/.asdf/shims/yarn
$ which node
/Users/atroschinetz/.asdf/shims/node
$ which go
/Users/atroschinetz/.asdf/shims/go

😬

Please no. I only installed the ruby plugin to asdf by conscious choice. I did not agree to this. I removed the plugins. A few days later and they're back again.

😬

I then found out the culprit is a simple gdk install.

😢

Proposal (optional)

Do NOT install asdf plugins just because you find asdf on the system. Leverage the plugins if they exist, sure.

Add an option to choose to have gdk install install plugins. Inform the user which plugins are being installed and when.

This is also what the contributor to asdf itself recommended to me: https://github.com/asdf-vm/asdf/issues/838#issuecomment-748676116

Environment (optional)

  • Operating System: macOS
Edited by Amy Troschinetz