On 15/07/2009, at 1:44 AM, ACTRAiSER wrote: > The question is why delayed_job must be bundled within thinking sphinx > at all instead of accessing the individual gem which the user must > then install to use ts?
I vendored delayed_job for two reasons: * to keep delayed deltas as simple as possible to get going * to avoid errors should the gem version have major changes that would cause TS to break. As you've found, the first version isn't always the case, if people are already using DJ. Moving forward, I'd like to remove the vendored version, let people install the gem themselves, I've just not gotten around to doing that yet. > Also is there a painless possibility to avoid the warnings without > touching either of the two gems, e.g. by configuration or some rails > code in environment.rb or in an initializer? Hmm, the only way I can think of is to maybe wrap the entire environment.rb within a silence block, but that's going to hide any other warnings as well, which obviously is not a good thing. Try removing TS's vendored copy, see if everything runs smoothly. -- Pat --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/thinking-sphinx?hl=en -~----------~----~----~----~------~----~------~--~---
