https://bugzilla.redhat.com/show_bug.cgi?id=2238191
--- Comment #14 from Daniel Milnes <[email protected]> --- (In reply to Daniel Milnes from comment #13) > (In reply to Tom Rix from comment #12) > > why was the specfile name changed ? > Having re-read the Golang Packaging Guidelines, I think I was wrong with my > original name for this package. I've renamed it to the version generated by > the %{goname} macro. Just to add to this, the packaging guide says the following: > Source packages that provide a well-known application such as etcd MUST be > named after the application. End users do not care about the language their > applications are written in. But do not name packages after an obscure > utility binary that happens to be built by the package. I don't think this qualifies as "well-known", as even Prometheus doesn't have its package named like this. I'm happy to change it back through if you feel it does meet this definition. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2238191 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202238191%23c14 -- _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
