well find another solution that works right:
require 'rubygems' gem 'sipXconfig-agent' require 'main' On Mon, May 14, 2012 at 2:16 PM, Domenico Chierico <[email protected]> wrote: > I can describe how it works now: > > sipxcallresolver uses fixed path to the right file: > > CallResolverMain:=/opt/build/lib/ruby/gems/1.8/gems/sipxcallresolver-2.0.0/lib/main.rb > > don't uses the gem's require strategies: > > require 'main' > > instead > > sipxconfig-agent (that is ruby script), just uses > > require 'rubygems' > require 'main' > > in this way the script has no such infos to select the right package, > and can be resolved as: > > /opt/build/lib/ruby/gems/1.8/gems/sipxcallresolver-2.0.0/lib/main.rb > > or > > /opt/build/lib/ruby/gems/1.8/gems/sipxconfig-agent-1.0.0/lib/main.rb > > so my point is, which way we should solve this issue? > > - name change > - use just bash script to require the main of the ruby project > - some others solution I don't know about ruby and the rubygem world > > thanks > Domenico Chierico > > On Mon, May 14, 2012 at 1:47 PM, Douglas Hubler <[email protected]> wrote: >> On Mon, May 14, 2012 at 7:34 AM, Domenico Chierico >> <[email protected]> wrote: >>> 4.4 >>> >>> I'm using the ACD so the question is what is the better way to solve >>> this? Can I send a patch to rename the file in main-agent or something >>> like that? or can you remane it ? >> >> it's odd no one has ever reported CDRs and ACDs cannot run together. >> can you send any conclusive evidence? >> _______________________________________________ >> sipx-dev mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
