[Rock-dev] [rock] #481: syskit: problem with "use" within sub-profiles

[rock]

#481: syskit: problem with "use" within sub-profiles
--------------------+-----------------
Reporter: mago02 | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: base | Keywords:
--------------------+-----------------
I had the need that i define a upper "robot" profile, and specialize it in
sub-profiles for simulation and the "real" robot.

In the upper-profile i want do define generic robot defines like "wall-
servoing", in the sub-profiles i want to specify needed use statements.

example:

generic:
define 'wall_servoing', Wall::Servoing

specialization:
use Wall::Servoing => Wall::Servoing.use(....)

I had _SOMETIMES_ the effect that this kind of specifications does not
work, so that i have to move the complete specification into the sub-
profile like:

define 'wall_servoing', Wall::Servoing.use(....)

This is from the need to not double code quite ugly and makes the use of
sub-profiles useless...

[rock]

#481: syskit: problem with "use" within sub-profiles
--------------------+------------------
Reporter: mago02 | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: base | Resolution:
Keywords: |
--------------------+------------------

Comment (by sylvain.joyeux):

You've nailed the main problem: sub-profiles are currently useless. I
would even go as far as "harmful" (i.e. don't use them in any complex
form). I've already fixed in in a much more elegant way than the current
system but (1) it is on the orogen_loaders branch and (2) I did not have
time to blog / announce it.

I'll try to prepare an override file for orogen_loaders and describe the
new syskit functionality in the next days.