Re:What will happen when we run out of names for JavaScript ...
by krapp on Saturday May 06, 2017 @05:37PM
(#14282403)
Even PHP manages to get this right - Composer uses the Packagist repository as a default but just about any git or svn repo with a URL will do.
Re:What will happen when we run out of names for JavaScript ...
by jaredsohn on Saturday May 06, 2017 @07:14PM
(#14282805)
npm supports git urls, too (or the even shorter user/project#tag if it is from github)
Re:What will happen when we run out of names for JavaScript ...
by manquer on Sunday May 07, 2017 @03:58AM
(#14284385)
Composer also supports namespacing
Re:What will happen when we run out of names for JavaScript ...
by shawnz on Saturday May 06, 2017 @05:41PM
(#14282425)
Does apt allow you to have multiple packages with the same name from different repositories? I don't see how it solves this issue otherwise.
Re:What will happen when we run out of names for JavaScript ...
by paulddraper on Saturday May 06, 2017 @05:50PM
(#14282459)
No, it does not.
But I don't use the vast majority of apt repos.
I use a handful of well-curated ones with high-quality software, plus a handful for one-off packages.
In contrast, there's basically no limit to how much debris you can upload to npm.
E.g. apt.