Merb Freezer is broken with merb-core MODE=rubygems
Reported by Matt Colyer | May 13th, 2008 @ 11:38 AM | in 0.9.7
This is #110 moved to the proper location.
Using 'rake freeze:core MODE=rubygems' installs the gems under framework/gems/merb-core-0.9.3. The correct behavior is to install under gems/.
I patch is attached for the correct behavior against the latest git.
Comments and changes to this ticket
-
Michael Klishin (antares) May 13th, 2008 @ 03:09 PM
- → State changed from new to open
- → Milestone changed from to 1.0
-

Matt Albright May 13th, 2008 @ 08:07 PM
Shouldn't line 56 of freezer_mode.rb also be changed to this:
`#{sudo} gem #{action} #{@component} --no-rdoc --no-ri -i #{freezer_dir}`
-

-
Michael Klishin (antares) May 14th, 2008 @ 09:08 AM
- → Assigned user changed from to Michael Klishin (antares)
Matt C.,
Git complains that your patch has no valid email address. I can apply it but if possible, configure git so we can give authors full credit ;)
-

Matt Colyer May 18th, 2008 @ 11:38 PM
I am a little worried about the spam problem, are the addresses obscured?
-
Eric White May 26th, 2008 @ 04:02 PM
commit 695dc198f7162e3256d6450ca0cec7e294cbf97f
Starting with that commit, I noticed the following issue.
I was expecting the 'gem install' to use a gem from the local gem repository, but it instead, will go to the internet to download the latest gems. This has a bad side affect that if for example you are on merb Edge and then rake freeze:core, you end up with merb-core_0.9.3. instead of the Edge version installed locally.
I found two ways to fix this.
One run a local gem server and add this to the sources list. But works with the current code base.
The second way is to switch to $GEM_HOME/cache, before running the 'gem install' on line 56. This works because gem will look in the current directory for a gem to install. This requires code changes to allow the user to specify $GEM_HOME/cache or, for example another directory containing gems.
Does anyone else have that issue?
-
Michael Klishin (antares) August 2nd, 2008 @ 01:49 PM
- → Title changed from Merb Freezer 0.9.3 broken with merb-core MODE=rubygems to Merb Freezer is broken with merb-core MODE=rubygems
- → Milestone changed from 1.0 to 0.9.6
- → Tag changed from to frozen-merb patch
-
Michael Klishin (antares) September 8th, 2008 @ 07:20 PM
- → Milestone changed from 0.9.6 to 0.9.7
-
Matt Aimonetti (mattetti) September 9th, 2008 @ 10:00 AM
- → State changed from open to resolved
Merb-freezer is deprecated as of 0.9.6. Instead Merb now supports booting from bundled gems from ./gems
We are working on thor tasks to handle most of bundling tasks:
http://github.com/mattetti/merb-...
Tasks will be made available when thor installer will be fixed and the tasks fully tested. (thor namespacing is currently broken when installing a namespaced task, put the thor task file in your app and do thor -T to see the available tasks)
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
