[omniORB] omniORBpy: Howto install modules independently?

[W. Borgert]

Thanks for your quick reply.  I think, both solutions are OK.
Some open points remain, see below.

Quoting Duncan Grisby <duncan at grisby.org>:
> That's a rather tricky situation. To be neat, you could make it so
> that the install rewrites the __init__.py files in the right way, just
> like omniidl itself does.

Could you elaborate a little bit on the algorithm?  omniidl has
the advantage of knowing the IDL.  At install time, I don't have
the IDL, because it may not part of the software package.

I assume, the best would be a tool 'install-omniORBpy-module'
called with the name of the _idl.py file and (if necessary) the
IDL module prefix, like A::B::C.  In addition, I would need an
uninstall-omniORBpy-module tool.

Scary...

> I possibly simpler solution is to become a bit omniORB specific and
> directly import the *_idl.py modules before importing the X and Y
> packages. If you do that, you don't need the X package directory at
> all.

I will try that.  I'm not opposed to using omniORB specific
import statements, because we don't plan using Python-ORBit or
Fnorb.  Two questions: Do I have to change anything else than
the import statements in the code?  If I have a lot of nested
IDL modules, do I have to import every single module?

Cheers, W. Borgert