Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Makes the gem system understand development vs. runtime dependencies [#…
…2195 state:resolved] The patch also fixes: * Fixes the chicken/egg problem present in the current gem system when gems are defined in the config that are not yet installed. * Remove the need to have hoe as a dependency of your production app. * Makes the gem 'unpacking' system a lot less fragile. Signed-off-by: Matt Jones <al2o3cr@gmail.com> Signed-off-by: Pratik Naik <pratiknaik@gmail.com>
- Loading branch information
Showing
5 changed files
with
163 additions
and
152 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
99d75a7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You have just made my day. Thanks!
99d75a7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect this commit might have broken vendored gems which are C extensions and haven’t been built yet. This causes “rake gems”, “rake gems:build”, and of course “script/server” to not work. To fix the problem you would run “rake gems:build”, but seeing as that’s broken too, you have to manually copy the built extension into the right place.
For the full details, see:
http://rails.lighthouseapp.com/projects/8994/tickets/2266