[Rock-dev] roby shell

[Chris Müller]

Uh, I currently realize you've also try it, sorry :].

But maybe someone can confirm / disprove my idea.

Chris


On 06.01.2012 06:19, Chris Müller wrote:
> Hi Allan,
>
> i've tried something which results maybe in an interesting hint about 
> that problem. If we try to start it from a complete
> NEXT flavor, you get your error message instantly.
>
> I've simple changed now the branch for tools/roby to MASTER in order 
> to observe the behaviour. It takes some seconds and
> results in another error message (of course due to some 
> incompabilities between next / master).
>
> $ ./scripts/shell
> 05:51:17.422 (Robot) turning ON MQueue usage
> /home/chris/repos/avalon_next/tools/utilrb/lib/utilrb/module/const_defined_here_p.rb:9:in 
> `const_defined?': nil is not a symbol (TypeError)
>     from 
> /home/chris/repos/avalon_next/tools/utilrb/lib/utilrb/module/const_defined_here_p.rb:9:in 
> `const_defined_here?'
>     from 
> /home/chris/repos/avalon_next/tools/utilrb/lib/utilrb/module/define_or_reuse.rb:13:in 
> `define_or_reuse'
>     from 
> /home/chris/repos/avalon_next/tools/roby/lib/roby/interface.rb:146:in 
> `reconnect'
>
> I think it's very interesting to see it is processing some seconds in 
> the background and outputs a simple message from the robot logger.
> In that case i've a feeling it already accomplish the drb 
> initialization, which would be hint for: a patch for the shell is only 
> included on the master branch.
>
> That's of course very uncertain and it would be better to test it 
> directly with a complete master flavor. Unfortunately switching and 
> rebuild
> to MASTER and back to NEXT is very time consuming :/. But i can 
> already confirm the shell is working on MASTER on our autoproj setup for
> RIMRES.
>
> Are we actually the first project, who is using Rock completely on 
> Next? :]
>
> We could maybe test it on AVALON itself; I didn't delete there our old 
> master flavor ...
>
> Chris
>
>