Rubygems shoudl already be required by the time init.rb is loaded.
But in the general case dependency is kinda broken on some versions of
rubygems. SO for now I recommend just using require unless you need to
specify a version.
-Ezra
On Apr 22, 2008, at 10:16 AM, James Herdman wrote:
> Hey gang.
>
> Jed noticed an issue with the 'dependency'/'dependencies' macro the
> other day when working on the Collective wiki. Namely, if you make
> RedCloth a dependency Merb gets a little cranky. I think I have
> this figured out when doing some mods to Collective today too.
> However, before I go trying to fix this in Merb, I wanted to run
> this by the community.
>
> The problem is simple: RedCloth requires you first load Rubygems.
> That is...
>
> Hey Jed.
>
> I think I have this 'dependency' and RedCloth thing figured out.
> When I was trying to make the Viking gem a dependency Merb
> complained. Do you know what both RedCloth and Viking (gem)
> require? Rubygems! That is...
>
> # In IRB...
> irb> require 'redcloth'
> LoadError: no such file to load -- redcloth
> from (irb):1:in `require'
> from (irb):1
> from :0
> irb> require 'rubygems'
> true
> irb> require 'redcloth'
> true
>
> My question is this: do we change the dependencies macro to load
> rubygems when this happens, or do we ignore it and demand that the
> user explicitly require a library outside of the dependencies macro
> (see http://github.com/meekish/collective/tree/master/config/init.rb#L25
> for an illustration)?
>
> James H.
> _______________________________________________
> Merb-devel mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/merb-devel
- Ezra Zygmuntowicz
-- Founder & Software Architect
-- [EMAIL PROTECTED]
-- EngineYard.com
_______________________________________________
Merb-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/merb-devel
