Hi all, Can I ask you guys what is the point of having config.frameworks in environment.rb? According to the comment before this config parameter, it is there so you can specify which frameworks you don''t want to use. On the other hand, if you use gem version of rails, and I believe most people do, whenever you require ''initializer'', all rails frameworks are being loaded as a part of gem dependencies mechanism. So basically this config parameter is useless and confusing. Please correct me if I''m wrong. Thanks. Kent.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Dec 12, 2005, at 11:21 PM, Kent Sibilev wrote:> Can I ask you guys what is the point of having config.frameworks in > environment.rb? According to the comment before this config > parameter, it is > there so you can specify which frameworks you don''t want to use. On > the other > hand, if you use gem version of rails, and I believe most people > do, whenever > you require ''initializer'', all rails frameworks are being loaded as > a part of > gem dependencies mechanism. So basically this config parameter is > useless and > confusing.Put your vendor/rails directory to work with rake freeze_gems or freeze_edge. jeremy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (Darwin) iD8DBQFDnwv0AQHALep9HFYRAszzAJwIoUcZEfTmW4T/BGRyEqaTAyovrwCgjghx IMalZk0BV2bgWcECsBUc4vk=81Sx -----END PGP SIGNATURE-----
Jeremy, I won''t help. The thing is that Rails::Initializer requires ruby_info.rb. ruby_info.rb is written in a way that as soon as you require it, it will load all frameworks. So even by not using gems at all, this config parameter still doesn''t work as advertised. Kent. On Tuesday 13 December 2005 12:59, Jeremy Kemper wrote:> On Dec 12, 2005, at 11:21 PM, Kent Sibilev wrote: > > Can I ask you guys what is the point of having config.frameworks in > > environment.rb? According to the comment before this config > > parameter, it is > > there so you can specify which frameworks you don''t want to use. On > > the other > > hand, if you use gem version of rails, and I believe most people > > do, whenever > > you require ''initializer'', all rails frameworks are being loaded as > > a part of > > gem dependencies mechanism. So basically this config parameter is > > useless and > > confusing. > > Put your vendor/rails directory to work with rake freeze_gems or > freeze_edge. > > jeremy > _______________________________________________ > Rails-core mailing list > Rails-core@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-core
Kent, On 12/13/05, Kent Sibilev <ksruby@gmail.com> wrote:> Jeremy, > > I won''t help. The thing is that Rails::Initializer requires ruby_info.rb. > ruby_info.rb is written in a way that as soon as you require it, it will load > all frameworks. So even by not using gems at all, this config parameter still > doesn''t work as advertised. > > Kent.Only version.rb is required for each framework. See Rails::Info#component_version (railties/lib/rails_info.rb, line 28). -- sam
Yes, you are right. Sorry for the noise. Kent. On Tuesday 13 December 2005 14:51, Sam Stephenson wrote:> Kent, >> Only version.rb is required for each framework. See > Rails::Info#component_version (railties/lib/rails_info.rb, line 28). > > -- > sam > _______________________________________________ > Rails-core mailing list > Rails-core@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-core