Using .gemspecs as Intended

Using .gemspecs as Intended « Katz Got Your Tongue?:

Luis Lavena , Posted April 2, 2010, 5:31 pm I would have to disagree with you Yehuda on this. For some gems, the scenario you’re presenting will work, for others, it wouldn’t. Let’s ignore for a second that bundler doesn’t like gems with native extensions or specific platform gems that got bundled, let’s talk about the gemspec. Gem::Specification get serialized inside the gem as YAML, and I’ve seen lot of people using things like Rake::FileList to build gemspecs, which fails. A concrete example can be found here: http://github.com/technicalpickles/jeweler/issuesearch?state=open&q=rake-compiler#issue/73 Also, gem build will not take in consideration special and external dependencies your gem might require that are not bundled with a simple gem build but that are pulled and generated when you do a “rake gem” command. For example, a ragel parser based extension. The whole ide...

Full article: http://yehudakatz.com/2010/04/02/using-gemspecs-as-intended/