3 ms·
> Doesn't this bifurcate the namespace of literally every packaging system they are supporting No. Unless you consider the URL the namespace, but it's not. E.
by paulddraper 8y ago
> Doesn't this bifurcate the namespace of literally every packaging system they are supporting
No. Unless you consider the URL the namespace, but it's not.
E.g. I can download the deb "vscode" from https://packages.microsoft.com/repos/vscode https://packages.microsoft.com/repos/vscode
Or I could download that it from a GitHub-user controlled URL, or someone's random website. The name of the package is still "vscode", regardless of what location it was fetched from.
- jacques_chester 8y ago> No. Unless you consider the URL the namespace, but it's not. It is for docker images. `foo/bar` is implicitly `hub.docker.com/foo/bar`.
- paulddraper 8y agoTrue. I think people are pretty well accustomed to that though. Dockerhub, AWS ECR, Google Cloud, etc.
- jacques_chester 8y agoYes and no. It affects software that's installed via things like Kubernetes pod definitions. You need to "relocate" images to the correct registry in that case. This is a sufficient hassle that one of my colleagues maintains an entire tool devoted entirely to this purpose: https://github.com/pivotal/image-relocation https://github.com/pivotal/image-relocation
- paulddraper 8y agoPoint being that Github doesn't really add any problem that doesn't exist in spades.