| Issue 118: | config.gem should be utilized from Rails 2.1 | |
| 2 people starred this issue and may be notified of changes. | Back to list |
Rails 2.1.0 allows you to specify gems that are packed / required by the
application.
Attempted to do a quick pass and add this, but after adding the following
to environment.rb...
config.gem('RedCloth')
config.gem('fastercsv')
config.gem('mime-types')
config.gem('mini_magick')
config.gem('ezcrypto')
...I encountered some problems with 'mime-types', even though it was
installed. Rails didn't seem to think it was.
This standard facility should be used to require gems so users can just
type "rake gems:install" before the bootstrap process.
Nov 7, 2008
should I do a patch for this?
Nov 9, 2008
Be my guest! :)
Dec 13, 2008
using config.gem currently errs with the current version of engines [go figure]. This adds a custom way to do it, though.
Jan 16, 2009
looks like I missed mysql in that list
Jan 28, 2009
we could unpack several gems to vendor\gems, as well
Jan 28, 2009
Here's a patch with unpacked gems [except RedCloth] in the vendor\gems directory. rake test does something weird for me, so I'm unable to test it.
Jan 28, 2009
and here's a change to allow them to be used for rake tasks, as well
Jan 28, 2009
allow the same to work with mime-types, as well. My bad.
Feb 21, 2009
note that I'm not sure if this patch allows the "pre installed" gems to [yet] work with just rake tasks.
Aug 25, 2010
I think vendoring gems is long past due. It will cut down on the installation process and clear up that whole mess. Not sure these patches cleanly apply but I'll look into it.
Labels:
-Priority-Medium Priority-High Milestone-v1.3
|
Seth, seems like you needs to specify a lib parameter to it require a file with a name different that the gem itself. config.gem('RedCloth') config.gem('fastercsv') config.gem('mime-types', :lib => 'mime/types') config.gem('mini_magick') config.gem('ezcrypto')