[
https://issues.apache.org/jira/browse/PROTON-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway closed PROTON-1760.
-------------------------------
Resolution: Won't Fix
Although the ruby Gem guidelines http://guides.rubygems.org/name-your-gem/ say
the gem should be named "qpid-proton" rather than "qpid_proton", discussion at
http://qpid.2158936.n2.nabble.com/WARNING-proton-ruby-package-and-gem-name-change-td7673285.html
suggests that changing the name is not worth the disruption to users. Given
the minor nature of the change, we're going to leave it alone.
> [ruby-binding] the package name on rubygems.org does not follow conventions
> ---------------------------------------------------------------------------
>
> Key: PROTON-1760
> URL: https://issues.apache.org/jira/browse/PROTON-1760
> Project: Qpid Proton
> Issue Type: Wish
> Components: ruby-binding
> Affects Versions: proton-c-0.21.0
> Reporter: Jiri Daněk
> Assignee: Alan Conway
> Priority: Trivial
> Fix For: proton-c-0.22.0
>
>
> The rubygems.org name is currently {{qpid_proton}}. From a not-so-random
> sampling, it seems to me use of dashes is more common than that of
> underscores. Additionally, the package in PyPi is called
> {{python-qpid-proton}}.
> I propose renaming the ruby package to {{qpid-proton}} or
> {{ruby-qpid-proton}} or even {{qpid-proton-ruby}}. If possible, which it may
> not be, by now.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
