3 ms·
I never really understood why would they map package names to the sites that host the sources. It was obvious something like this was going to happen and it's h
by lukaslalinsky 11y ago
I never really understood why would they map package names to the sites that host the sources. It was obvious something like this was going to happen and it's happening on smaller scale all the time. Projects move.
- Gigablah 11y agoAnd even if projects stay at the same URL, their folder structures would change.
- danieldk 11y agoIn the Go packaging scheme, they shouldn't. The idea is that a URL is API-stable. Changing the folder structure changes the API (package names). For this reason, you have wrappers like http://gopkg.in/ http://gopkg.in/ , which permit some freedom in the form of git tags. (I fully agree that Go packaging is very sensitive to API changes and incidents like sites disappearing altogether.)
- manojlds 11y agoLess impactful, but docker images have to be tagged with the docker registry URL they will be pushed to.
- lukaslalinsky 11y agoThat's another thing I always disliked. I'd have preferred a configurable prefix, or something like Git remotes.
- cfstras 11y agoThe idea was that people should never make API-breaking changes for URLs and instead offer only new interfaces or make a new package at a different URL. Funny coincidence that google itself broke that idea.