From: Eric Hodel <drbrain@...7.net>
Date: 2009-04-14T06:04:12+09:00
Subject: Re: how do you manage your gems' gemspecs?

On Apr 9, 2009, at 20:00, ghorner wrote:

>  I'm curious how people manage creating their gemspecs. I'm not
> asking for a flame war on gem creators i.e. hoe vs newgem vs jeweler.
> I'm just wondering if your gem creators encourage creating Rakefiles
> with some gemspec configuration inside of it. If so, how do you do
> this gem after gem and not get annoyed that you're not being DRY?
> I ended up going with a solution where I generate all my gem's
> gemspecs from one config file: http://github.com/cldwalker/dotfiles/blob/master/.gems.yml 
> .

This makes it harder for other people to develop with your gems.  Now  
they need two things in order to build your gems if they want to  
install a gem.

Using globs is a bad idea, you end up including files you don't want  
in your gem.  A manifest file that gets automatically checked at  
release time solves this problem elegantly.

> I wrote more about my solution here:
> http://tagaholic.me/2009/04/08/building-dry-gems-with-thor-and-jeweler.html
> How do you manage your gems' gemspecs?

I keep them per-project and largely generate them from the non-Rakefile:

Hoe.new('gmail_contacts', GmailContacts::VERSION) do |p|
   p.rubyforge_name = 'seattlerb'
   p.developer 'Eric Hodel', 'drbrain@segment7.net'

   p.extra_deps << ['gdata', '~> 1.0']
   p.extra_deps << ['nokogiri', '~> 1.2']
end

description, summary, and homepage are all figured out for me from the  
README.txt