# Freeze extra gems? **URL:** \ **Category:** Rails\ **Created:** [March 27, 2007, 8:03pm UTC](https://www.ruby-forum.com/t/freeze-extra-gems/90318 "2007-03-27T20:03:27Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![BallS\_Donald\_A\_Jr\_S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/da6949/32.png) [@BallS\_Donald\_A\_Jr\_S](https://www.ruby-forum.com/u/BallS_Donald_A_Jr_S)\ **Post date:** [March 27, 2007, 8:03pm UTC](https://www.ruby-forum.com/t/freeze-extra-gems/90318/1 "2007-03-27T20:03:27Z")
I’m just now getting around to freezing rails into my app. Is there a way to freeze extra gems into my app as well, e.g. ezcrypto or even the dreaded rmagick? - donald ---
**Author:** ![BallS\_Donald\_A\_Jr\_S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/da6949/32.png) [@BallS\_Donald\_A\_Jr\_S](https://www.ruby-forum.com/u/BallS_Donald_A_Jr_S)\ **Post date:** [March 27, 2007, 8:49pm UTC](https://www.ruby-forum.com/t/freeze-extra-gems/90318/2 "2007-03-27T20:49:34Z")
On Tuesday 27 March 2007, Ball, Donald A Jr (Library) wrote: > I’m just now getting around to freezing rails into my app. Is there a > way to freeze extra gems into my app as well, e.g. ezcrypto or even > the dreaded rmagick? Yes, look for the gemsonrails gem. Michael – Michael S. [mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) [http://www.schuerig.de/michael/](http://www.schuerig.de/michael/) ---
**Author:** ![BallS\_Donald\_A\_Jr\_S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/da6949/32.png) [@BallS\_Donald\_A\_Jr\_S](https://www.ruby-forum.com/u/BallS_Donald_A_Jr_S)\ **Post date:** [March 27, 2007, 9:32pm UTC](https://www.ruby-forum.com/t/freeze-extra-gems/90318/3 "2007-03-27T21:32:40Z")
On 3/27/07, Ball, Donald A Jr (Library) [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > I’m just now getting around to freezing rails into my app. Is there a > way to freeze extra gems into my app as well, e.g. ezcrypto or even the > dreaded rmagick? Just posted today: [http://errtheblog.com/post/2120](http://errtheblog.com/post/2120) – Chris W. > **[err.the\_blog](http://errtheblog.com)** > > Err the Blog: Ruby and Rails from the front. ---
**Author:** ![BallS\_Donald\_A\_Jr\_S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/da6949/32.png) [@BallS\_Donald\_A\_Jr\_S](https://www.ruby-forum.com/u/BallS_Donald_A_Jr_S)\ **Post date:** [March 27, 2007, 10:03pm UTC](https://www.ruby-forum.com/t/freeze-extra-gems/90318/4 "2007-03-27T22:03:55Z")
> > I’m just now getting around to freezing rails into my app. > > Is there a > > way to freeze extra gems into my app as well, e.g. ezcrypto or even > > the dreaded rmagick? > > Just posted today: [http://errtheblog.com/post/2120](http://errtheblog.com/post/2120) Ooh, synchronicity. Thanks! Both this and gemsonrails look simple and elegant. I reckon I’d lean towards the latter since it’s a self-contained gem instead of a small set of manual patches. Is there some reason I might want to consider that instinct? - donald ---
**Author:** ![BallS\_Donald\_A\_Jr\_S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/da6949/32.png) [@BallS\_Donald\_A\_Jr\_S](https://www.ruby-forum.com/u/BallS_Donald_A_Jr_S)\ **Post date:** [March 27, 2007, 10:50pm UTC](https://www.ruby-forum.com/t/freeze-extra-gems/90318/5 "2007-03-27T22:50:07Z")
On 3/27/07, Ball, Donald A Jr (Library) [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Ooh, synchronicity. Thanks! Both this and gemsonrails look simple and > elegant. I reckon I’d lean towards the latter since it’s a > self-contained gem instead of a small set of manual patches. Is there > some reason I might want to consider that instinct? Really, whatever you feel more comfortable with. There are a few solutions listed in that post and they all have a different flavor but ultimately achieve the same goal. As long as you know what’s going on, do what feels best. – Chris W. > **[err.the\_blog](http://errtheblog.com)** > > Err the Blog: Ruby and Rails from the front.