[omniORB] omniORBpy: Howto install modules independently?

[Duncan Grisby]

On Friday 19 March, "W. Borgert" wrote:

> I have a general question on how to handle multiple generated Python files.
> I have two software packages, A and B, both containing omniORBpy-based
> software.  Both software packages must be installable independently of each
> other.  In both software packages the software is based on some IDL files,
> in package A:
> 
> module X {
>   module Y {
>     interface A { ... };
>   };
> };
> 
> And in package B:
> 
> module X {
>   module Y {
>     interface B { ... };
>   };
> };
> 
> The problem is in the generated __init__.py files.  Package A installes
> an X/__init__.py and Y/__init__.py, but package B will try to install
> the same file, but with different content.  How to handle this conflict?
> Thanks in advance!

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.

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.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --