glide rm and glide get

[zjn1234]

1. when i run glide get xxxx glide will not only get the xxxx package to glide.yaml but also update other packages
2. when i run glide rm xxxx glide will not only rm xxxx package from glide.yaml but also remove more packages

[zjn1234]

can anybody explain this question

[cafra]

me too

[nidhi-ag]

I am also facing this issue. On removing levelDB package it is removing other packages or their sub-packages also

[jmelfi]

not a dev here but is the package you are removing (leveldb or xxxxx package) the only package that uses those other vendored deps?

I've seen this happen as intended to ensure that the compatible deps are available. I've not run into this particular issue myself in the case you're describing.

Are you not able to build after glide rm xxxxx or do you need to run a glide i to get it back to it's normal state?

To be clear, the help document describes rm and get as the inverse operation of each other.

Get installs a package into vendor and generates the glide.lock file with that added dependency. Remove uninstalls a package and generates the new glide.lock file based on the new dependencies with that removed package.

This is at least my understanding.