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

On Apr 10, 2:13 pm, Luis Lavena <luislav...@gmail.com> wrote:
> On Apr 10, 2:20 pm, cldwalker <gabriel.hor...@gmail.com> wrote:
>
>
>
> > > DRY is a useful principle, but when the code required to implement it  
> > > is larger than repeating something simple you might consider whether  
> > > it's appropriate.    In this case the things you are trying to avoid  
>
> > Actually the code required to implement it is 60 lines (1/4 spent on
> > documentation):http://github.com/cldwalker/thor-tasks/blob/8901b806cbdacd30b6dcbf92c...
>
> > > repeating are simple and memorable - such as your own name.   There's  
> > > also the concern that anyone building your gem might accidentally be  
> > > labeled as the original author.   There are other valuable principles  
> > > you might want to balance, such as the KEIOPSPCFIE (keep everything  
> > > in one place so people can find it easily ) principle.
>
> > I probably didn't make it clear but I would still be shipping my gem's
> > with their gemspec.
> > I just prefer generating them from one central location. This
> > principle would be preserved since I ship gems with their gemspec.
>
> Well, what happens if I configure the central location in my machine
> with different values than yours?
>
> The thing is that you're generating the gemspec for that gem from a
> central location. We all know that the gemspec gets bundled with the
> gem itself, the problem is the generator tasks and the obscure process
> of updating the gemspec without knowing where the central location is.
>
> Sometimes DRY is overrated.
>
> --
> Luis Lavena

If you look at the gemspec_update task in my post, you'll see that the
gemspec values won't differ.
There's nothing obscure about doing rake gemspec_update.

Gabriel