You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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:
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
andAcme::Leeway
all in the tradition of Perl's Acme::* libs. All of which are listed as requirements of the baseAcme
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.
The text was updated successfully, but these errors were encountered: