Martin & Josh,
Thanks for the assistance!
Actually, I wasn't looking at this from the developer standpoint but
more the end-user standpoint. I've been trying to figure out how the
two approaches for installing gems "work" and what issues are
involved. For example, if I have
config.gem 'authlogic'
in my config/environment.rb file and then months later I add
config.gem 'hoptoad'
to the config/environment.rb file and do a "rake gems:install" will it
try to re-install or update authlogic? That kind of thing...
Sorry for any confusion!
Ken
On Jan 27, 2010, at 3:07 PM, Martin Emde wrote:
+1 for bundler.
it is most likely the way you'll handle all your gems moving forward.
Martin Emde
Tw: @martinemde
On Wed, Jan 27, 2010 at 2:50 PM, Josh Lubaway
<[email protected]> wrote:
I feel that bundler is worth mentioning here.
The use of config.gem will be deprecated in Rails 3. And you can use
bundler in your rails apps today:
http://yehudakatz.com/2009/11/03/using-the-new-gem-bundler-today/
-Josh
On Wed, Jan 27, 2010 at 2:28 PM, Justin James Grevich <[email protected]
> wrote:
Hi Ken,
Here are some links that should answer your questions:
http://guides.rubyonrails.org/2_2_release_notes.html#configgems
http://ryandaigle.com/articles/2008/4/1/what-s-new-in-edge-rails-gem-dependencies
Let me know if you come across any better references.
justin
On Jan 27, 10:39 am, Ken Hudson <[email protected]>
wrote:
> Hi Everyone,
>
> For most of my time working with Rails I have installed gems using a
> command like this from the command line:
>
> sudo gem install blahblah
>
> and this has worked great.
>
> Now I am seeing more and more install instructions for gems that
call
> for adding a line like
>
> config.gem 'blahblah'
>
> to your config/environment.rb file and then entering the following:
>
> rake gems:install
>
> Why the difference? What are the advantages to the second approach?
> If you have have multiple lines in config/environment.rb file like:
>
> config.gem 'abcdef'
> config.gem 'xyzzzz'
>
> and then run "rake gems:install" will existing gems be reinstalled
or
> updated? If yes, how do you prevent this from happening?
>
> I suppose these questions might fall into the "dumb" category but I
> don't know the answers and I'd like to learn more about how this
works.
>
> Thanks, Ken
--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
http://www.nealstreetdesign.com
http://www.shareastronomy.com
--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
