I wrote a patch a while back that handles metadata. I'm not sure what's become 
of it.

-Erik

On Oct 13, 2011, at 9:41 AM, Nick Quaranto wrote:

> Erik, not sure what you're referring to...
> On Oct 13, 2011 12:28 PM, "Erik Hollensbe" <e...@hollensbe.org> wrote:
> 
>> 
>> Did my patch get reverted?
>> 
>> -Erik
>> 
>> On Oct 13, 2011, at 9:17 AM, Nick Quaranto wrote:
>> 
>>> "dependency" is for "gem" dependency, let's keep it that way, please.
>> There
>>> is a "requirements" field in the gemspec that this could be used for
>>> instead:
>>> 
>>> http://guides.rubygems.org/specification-reference/#requirements
>>> 
>>> However this is yet another reason to have metadata :(
>>> 
>>> -Nick
>>> 
>>> On Thu, Oct 13, 2011 at 11:47 AM, Charles Oliver Nutter <
>> head...@headius.com
>>>> wrote:
>>> 
>>>> I ran into a snag trying to demo JRuby's support for installing Maven
>>>> artifacts as gems: rubygems.org does not allow pushing gems with
>>>> external dependencies.
>>>> 
>>>> For the "cloby" gem, which exposes Clojure's STM and persistent list
>>>> as Ruby instance variables, I wanted to have a dependency on Clojure
>>>> directly from Maven, using JRuby's maven gem support. The gem name for
>>>> that looks like "mvn:org.clojure:clojure". This worked well as a
>>>> dependency in the gemspec, and local copies of the gem would also
>>>> fetch Clojure from Maven Central. But I was not able to push the gem
>>>> to rubygems.org.
>>>> 
>>>> Inability to push gems that depend on Maven artifacts waters down that
>>>> support considerably. It also means we would need to start pushing
>>>> Maven libraries to Rubygems.org for every such library anyone depends
>>>> on...which could mean hundreds of gems that only exist to wrap a JVM
>>>> library. I know nobody wants that (and that's why we built this
>>>> support into JRuby) so perhaps we can reach a compromise?
>>>> 
>>>> - Charlie
>>>> _______________________________________________
>>>> RubyGems-Developers mailing list
>>>> http://rubyforge.org/projects/rubygems
>>>> 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
>> 
>> _______________________________________________
>> RubyGems-Developers mailing list
>> http://rubyforge.org/projects/rubygems
>> 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

_______________________________________________
RubyGems-Developers mailing list
http://rubyforge.org/projects/rubygems
RubyGems-Developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers

Reply via email to