On Sat, Sep 20, 2008 at 8:46 PM, Blake Watters <[EMAIL PROTECTED]> wrote: > If the optional gem is common, why not a config.optional_gem method? Covers > all bases explicitly and succinctly.
This was discussed in a recent thread. Rubygems already provides a way to flag development gems. Aside from that, any determiniation of "optional" is developer-, platform- or environment- specific, and is best handled with custom code in the environment file(s). In any of these cases, you would need some custom code anyway to determine whether the non-development "optional" dependency is actually required or not (inclusion in a specific environment file rather than environment.rb, platform check, env var check, etc). So, if you need custom code anyway, just write your own conditional to not even execute the optional config.gem call. No need for a separate method. -- Chad --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
