Release your gems to RubyForge, no pain involved.
Joe assumes you have a .gemspec file in the current directory and it will use it to build the gem. Once you have it, try this:
$ thor joe:package
Congratulations, you should have your gem built and an archive copy inside the
Now go ahead and release your new gem to RubyForge:
$ thor joe:release
Easy, right? Wait a few minutes until RubyForge updates its gems index and you will be able to run
sudo gem install foo.
If you get an error about a missing
group_id, try running
rubyforge config. This hooks up your RubyForge account with the gem and configures where to release it.
Maintaining a gemspec file
The easiest way we've found to maintain a gemspec file is by creating a
foo.gemspec.erb template (see example). Then you can use a Thor task to produce the real gemspec file:
$ thor joe:gemspec
You need the
rubyforge gem in order to release files. If you don't have it already:
$ sudo gem install rubyforge $ rubyforge setup $ rubyforge config
Make sure you have Thor installed:
$ sudo gem install thor
And then simply:
$ thor install http://dimaion.com/joe/joe.thor
That's it. Try:
$ thor -T
And you will get a list of Thor tasks.
Thanks to Blake Mizerany for pointing us to the Sinatra Rakefile for reference.
Copyright (c) 2009 Damian Janowski and Michel Martens
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.