From: cldwalker <gabriel.horner@...>
Date: 2009-04-10T13:55:03+09:00
Subject: Re: how do you manage your gems' gemspecs?

Nice rake task. I didn't know github gems allow for yaml gemspecs. For
me it's worth having one gemspec config file outside of my gem
directory in exchange for being DRY i.e. not having to write the same
common gemspec attributes for every gem.

Gabriel

On Apr 9, 11:52 pm, Luis Lavena <luislav...@gmail.com> wrote:
> On Apr 9, 11:57 pm, ghorner <gabriel.hor...@gmail.com> wrote:
>
> > Hi,
> >   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.
> > I wrote more about my solution here:http://tagaholic.me/2009/04/08/building-dry-gems-with-thor-and-jewele...
> > How do you manage your gems' gemspecs?
>
> Manually built... nah, just kidding ;-)
>
> rake-compiler gemspec is strictly YAML, and plays as a manifest file
> so there is no glob in that.
>
> I can diff it before committing, since every time the gemspec is
> updated the gem is generated in GitHub.
>
> http://github.com/luislavena/rake-compiler/blob/master/tasks/gem.rake
>
> I'm not fond for one place for everything as configuration files. The
> thing with that is that I need to go to some other place every time I
> need to update the gemspec or any kind of info.
>
> Just my two cents,
> --
> Luis Lavena