tibbs commented on the pull-request: `Fix goname generation to match versioning
guildelines` that you are following:
``
Yes, I never said I wouldn't approve them.
I have no idea why every Go package decided to do something different; I think the
guideline has been in place since before Go packages started entering the distribution,
but maybe there's a reason why Go can't follow it. I don't know. I would
assume some thought was put into the naming, or maybe the Go guidelines already document
that the scheme for those packages is different. (I haven't read them.)
If there is no good reason for the difference then it would be nice if Go packages
conformed to the same naming guidelines as other packages, **but** it may just be that
"changing things now is a massive pain" qualifies as a good reason. If so,
someone should simply take that to the packaging committee, explain what has happened, and
send a PR for the Go and naming guidelines describing the scheme. (The latter has
sections at the end describing issues for specific languages/ecosystems.)
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/55