2 ms·
With crates.io, users cannot delete their packages. They can 'yank' a version, which means that no new packages can depend on it, but existing packages can. So
by steveklabnik 11y ago
With crates.io, users cannot delete their packages. They can 'yank' a version, which means that no new packages can depend on it, but existing packages can.
So in this specific case, there are two packages: kik, the subject of the legal threat, and left-pad, another module by the same author. If we were compelled through legal means to remove a package, as administorators, we could, which is what happened with kik. However, if said author got mad at us, they couldn't _delete_ their other packages, only yank them, and so people's builds would not break, like they did here.
Does that make sense?
(IIRC Rubygems acts in the same way)
- sbuttgereit 11y agoIt does. Given that I've started a project in Rust which will have such dependencies, I feel even better that clearly there has been some good thinking put into this.