Re:Go vgo: Semantic Versioning and Human Error
by bennofs on Monday May 21, 2018 @05:20PM
(#17121929)
Other dep managers could at least tell you about the conflict. Maybe that's what vgo needs, a way to specify a conflict bound so that any downstream user is notified if the depgraph has conflicts (ofc conflict bounds would only apply after del resolution as simple checks otherwise it wouldn't be MVS)?
[ Parent
| on HN ]
Re:Go vgo: Semantic Versioning and Human Error
by tyrankh on Monday May 21, 2018 @05:47PM
(#17122130)
> Maybe that's what vgo needs, a way to specify a conflict bound
This is a valid idea; you should make a proposal or issue for it. Alternatively, it seems like something that would be easy to add separately - I personally like the idea of vgo as more of a simple, unix-like building block that you'd build on top of. Adding a small utility CLI checks incompatibilities with `vgo list` + some incompatibilities.txt file would be pretty easy.