This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
rick (author)
Mon May 05 23:55:10 -0700 2008
commit 9c2657aa96d3a8f19602ded748e558b0531c1132
tree 09c4f9eb8cae7d8e1dd1971e81672b9f88d28b51
parent 37599d16f2374179ebf001aeb79ff121e3d67519 parent e792d4ab70448f79142fdf492390682ff5ea6398
tree 09c4f9eb8cae7d8e1dd1971e81672b9f88d28b51
parent 37599d16f2374179ebf001aeb79ff121e3d67519 parent e792d4ab70448f79142fdf492390682ff5ea6398
... |
... |
|





Comments
I think this commit is causing the following error – http://pastie.caboo.se/pastes/195002 (pastied by mattly, but it matches what I was seeing in production)
and i had worked around that error by installing gems in my system repo instead of vendor/gems
Yup I can verify that this is happening for me too (see http://rails.lighthouseapp.com/projects/8994/tickets/122). Can a Rails committer re-open that ticket and possibly consider reverting this commit please? Thanks!
Oh yeah and my workaround was to stop using config.gem – I simply reverted to the bit of code I had to load gems in the vendor/gems directory that I was using prior to switching to config.gem.
to be fair—it actually is using my gems in vendor/gems, BUT it requires that they’re also installed in the system repo. I know this because i have a unpack of a gem that breaks on edge rails unpacked into vendor/gems and it actually uses that. but it complains if i don’t have it installed normally too.