On Thu, Jun 12, 2008 at 3:47 AM, Rick Olson <[EMAIL PROTECTED]> wrote: > In a similar vein: last night at the Baltimore ruby group, John > Trupiano suggested some way of merging the yml files from the > geminstaller gem with Rails' gem configurations.
I've wanted to provide a non-YAML config option for GemInstaller for a while, but it is down on the priority list. And, as pointed out, if the config is in Ruby (as it is with config.gems), then it's still easy to parse a YAML file (such as geminstaller.yml) to generate that config. That's probably the best approach to support what John wanted, and would be cool to have in Rails by default (patch someone?!?) After reading this thread, I'm convinced that both Ruby and YAML config should be supported (so I retract my -1 if that will be the case). All-ruby config is cool and nice, but for metadata describing external dependencies (Gems, Databases), there should be a STANDARDIZED, easily parsable, non-Ruby format supported as well. So, I hope Rails still natively supports the old YAML format after this patch, to support old tutorials, and to provide a standardized option when it is needed, such as Rails parsing geminstaller.yml if it exists, or a hosting company parsing geminstaller.yml or database.yml to auto-configure whatever... Also, I still don't think either option is DRY-er than the other, because YAML supports reuse, as was just pointed out. -- 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 rubyonrails-core@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
