From: cldwalker <gabriel.horner@...>
Date: 2009-04-11T02:15:07+09:00
Subject: Re: how do you manage your gems' gemspecs?

On Apr 10, 9:28 am, Luis Lavena <luislav...@gmail.com> wrote:
> On Apr 10, 1:51 am, cldwalker <gabriel.hor...@gmail.com> wrote:
>
> > 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
>
> In theory to be SAFE, the gem builder prefers YAML over Ruby code.
>
> Keeping the common attributes outside your repository reduces the
> clarity of your code since other users (besides you) can contribute
> with the project.
>
> Regards,
> --
> Luis Lavena

Luis,
  My one config file isn't keeping the common gemspec attributes
outside of the gem. I still generate and ship all of my gems with the
full gemspec. I just like to generate my gemspec from one central, DRY
location.

Someone brought up a similar point about not shipping my gem with its
meta gemspec i.e. the rake tasks that generate my gemspec using file-
related globs. I think that's a valid point so I updated the end of my
post with a solution to it(http://tagaholic.me/2009/04/08/building-dry-
gems-with-thor-and-jeweler). I basically generate from my central
config and ship with my gem a yaml containing globbish gemspec
attributes to be used by a rake task.

Gabriel