This project is archived and is in readonly mode.
config.gem does not scope search to gems path
-
Matt Jones
- Assigned user set to Matt Jones
The search path is not really something that we have that level of control over; note that a gem that triggers this is going to have problems anyways; the typical way of including many gems is
require 'filename'Which will automatically find the most recent gem that has that file. The idea (followed by most gems) is to have the filename be specific to the gem (in your case, it should be backupgem.rb or similar).
Can you provide a specific example of a gem that has this problem?
-
David Dollar
This definitely appears to be more of general gems issue rather than a Rails issue.
-
Ryan Bigg
- State changed from new to stale
Please re-open with an example if this is still causing problems.