Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I have an issue with the name of your gem/class ;) #1

Open
smathy opened this issue Nov 13, 2013 · 2 comments
Open

I have an issue with the name of your gem/class ;) #1

smathy opened this issue Nov 13, 2013 · 2 comments

Comments

@smathy
Copy link

smathy commented Nov 13, 2013

Hi,

I created the "Acme" namespace here in the Ruby world for just such gems as yours. Would you consider republishing it under the Acme::DoubleHelix name?

We already have: Acme::Bleach, Acme::Heisenberg and Acme::Leeway all in the tradition of Perl's Acme::* libs. All of which are listed as requirements of the base Acme gem for simple install.

If you're not interested, no problem, I'm happy to do the legwork for you, just thought I'd offer in case you were interested.

@mame
Copy link
Owner

mame commented Nov 14, 2013

I agree to clarify the category of gems. However, I don't think that a namespace is a good way of that. I guess few one will benefits even if I added just a line:

module Acme; module DoubleHelix; end; end 

to this code.

Rather, RubyGems should have the feature. It would be very good if the category information is included in gemspec and if we can filter gems with category specified:

gem search -c acme

@smathy
Copy link
Author

smathy commented Nov 14, 2013

So, you want to change RubyGems rather than namespace your gem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants