4 ms·
I feel like the article made its case pretty well, but I really dislike idea that I need to duplicate my library into a "v2/" directory (or a different top leve
by __david__ 9y ago
I feel like the article made its case pretty well, but I really dislike idea that I need to duplicate my library into a "v2/" directory (or a different top level git repo) in practice. Maybe I'm misunderstanding something, but this seems to be exactly what branches are for. If I'm not able to specify a branch name in the package "path" then there's something really wrong.
- matt_m 9y agoIt wasn't obvious to me either, but apparently vgo translates that into the appropriate git tag, it's not actually a separate directory.
- 4ad 9y agoYeah, it's just the import path that it's changed, but it's still ugly as sin and makes the mapping between import paths and filesystem paths non-trivial.