From: Juan Zanos Date: 2009-04-10T23:01:04+09:00 Subject: Re: how do you manage your gems' gemspecs? On 10 avr. 09, at 09:30, Luis Lavena wrote: > On Apr 10, 1:51 am, cldwalker 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 > 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 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. Best, Juan