This has been brought up before and we've rejected it. There is no reasonable way for rubygems to make sense of the values in requirements because their entirely system dependent.
In 2.0, gem metadata can be used to store these kinds of values for you to write a tool that will read them (which again will have to deal with the system dependent issues itself). - Evan -- Evan Phoenix // e...@phx.io On Saturday, January 26, 2013 at 9:08 AM, Jordi Massaguer Pla wrote: > Hi all, > > when deploying gems automatically it would be great if we could > somehow know which system requirements a native gem has. I've read in > the documentation that there is the requirements field that can be > used for that purpose. However, the requirements field is "free text", > and that makes it difficult to parse with an automatic tool. > > Then, I thought about sending a PR to the native gems we use so that > they have this information in a more "structred" way. For example, for > rmagick, the PR would add this to the gemspec: > > s.requirements = ["libMagick.so >= 6.6.0", "pkgconfig(libMagick) >= 6.6.0"] > > meaning that rmagick gem needs libMagick and libMagick-devel. > > What do you think on writing the requirements in such a way? Do you > have any recomendation on that? > _______________________________________________ > RubyGems-Developers mailing list > http://rubyforge.org/projects/rubygems > RubyGems-Developers@rubyforge.org (mailto:RubyGems-Developers@rubyforge.org) > http://rubyforge.org/mailman/listinfo/rubygems-developers > > _______________________________________________ RubyGems-Developers mailing list http://rubyforge.org/projects/rubygems RubyGems-Developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
