4 ms·
You should really take a look at Jeweler (http://github.com/technicalpickles/jeweler http://github.com/technicalpickles/jeweler) and MG (http://github.com/sr/mg
by mbleigh 16y ago
You should really take a look at Jeweler (http://github.com/technicalpickles/jeweler http://github.com/technicalpickles/jeweler) and MG (http://github.com/sr/mg http://github.com/sr/mg). They both make it extremely easy to maintain and publish gems to Gemcutter. Hoe was necessary back when RubyForge was the only gem host, but now that we have gem push it's not the simplest way.
- crazydiamond 16y agoThe other day while creating a new version for my gem, and getting hoe errors, i did look at the link above. It did not look so easy. Instead of creating a gemspec, or modifying my gemspec, i update the Rakefile and then generate a gemspec. I will try it out and see how it is. Again, should not ruby have one standard prescribed way of doing it, and not so many.
- bphogan 16y agoRuby does. Jeweler, Hoe, and other things are scaffolding for Gems. They get you going, but I found that as I relied on them too much I didn't really understand how it works. You can write a gemspec by hand which is what I have done now for my new gems that I'm working on. When I get time I will change the old ones to use a hand-rolled gemspec and a simple rake file for publishing. Gemcutter has made it trivial to take a hand-rolled gemspec and publish your gem. No libraries or gem scaffolding necessary.
- conorh 16y agoI don't really understand the need for Jeweler. Gemspec is a straightforward format and I've never had problems maintaing a gemspec by hand. It provides a version bumping rake task, but that is a single line edit in the gemspec.