Perils of gem creation and release
Seems every now and then someone comes up with a new way of creating a gem. However, these ways get obsolete very fast, so it can be frustrating. e.g. gemcutter’s
gem tumble command is outdated, by the way. Or was it
migrate (sorry cant remember), why not remove it, so squeamish people like me don’t squeam.
Every time I am releasing a new version of my gem, I start getting errors from hoe since they’ve changed their syntax. This time round, I was just unable to get it to work — some parameter mismatch.
A site I just looked at points me to the Gemspec Reference, but that doesn’t seem to give a sample. Hoe was giving errors since it keeps changing and the new suggested syntax is now suddenly borking. So i’ve gone ahead with Jeweler.
Jeweler gives me this error:
Jeweler not available. Install it with: sudo gem install technicalpickles-jeweler -s http://gems.github.com
Okay, so here goes:
sudo gem install technicalpickles-jeweler -s http://gems.github.com
ERROR: Error installing technicalpickles-jeweler:
technicalpickles-jeweler requires git (>= 1.2.1, runtime)
So i thought, lets just try jeweler itself …
$ sudo gem install jeweler
Successfully installed git-1.2.5
Successfully installed jeweler-1.4.0
2 gems installed
Phew. So now I can just create a gemspec using “
rake gemspec” and then “
rake build” to build it. I hope i won’t have to keep increment version numbers in gemspecs and the ruby file.
version_bump should do the trick. I hope by the time I’m ready for a new release, I won;t have to rewrite my Rakefile. The good thing is that my gemspec does not have a dependency with Jeweler (it did with hoe). Sorry for the rant !