Hi, this is not about this package, but rather about the general golang naming scheme. This ITP just triggered me to finally speak up… On Thu, Mar 31, 2016 at 09:23:07AM +1100, Dmitry Smirnov wrote: > Package name: golang-github-peterbourgon-diskv > URL: https://github.com/peterbourgon/diskv As you might have noticed, golang packages seem to have an, aehm, interesting naming scheme, where they basically take the upstream URL and turn this into a package name. This seems very very strange to me, not the least it makes me wonder what will happen if github renames itself to another company name or whatever URL changes might occur. It's also quite meaningless and leads to some strange package names like "golang-github-aws-aws-sdk-go-dev" which so far was the worst I've seen. I'm bringing this up now, because it seems we'll be getting more golang packages in the archive, at least if the trend (which can be seen nicely on https://tests.reproducible-builds.org/unstable/amd64/stats_meta_pkg_state_maint_pkg-golang-maintainers.png ) continues: ten months ago we had <100 golang packages in the archive, now there are more than 400… I wonder, is there any other justification other than lazyness? I also wonder, is there really a problem with this, except that it looks very strange and will break when (not if) URLs change? -- cheers, Holger
Attachment:
signature.asc
Description: Digital signature