requirements for native gems not free text?
Jordi Massaguer Pla
jmassaguerpla at suse.de
Sat Jan 26 18:06:45 UTC 2013
Quoting Evan Phoenix <evan at phx.io>:
> 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).
Does this mean we could have something like:
metadata["linux_requirements"] = ["libMagick.so >= 6.6.2"]
where can I find more information on the metadata?
> - Evan
> Evan Phoenix // evan at 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
>> RubyGems-Developers at rubyforge.org (mailto:RubyGems-Developers at rubyforge.org)
> RubyGems-Developers mailing list
> RubyGems-Developers at rubyforge.org
More information about the RubyGems-Developers