[omniORB] building omniORBpy

[Arnault Bonafos]

Hello,
I have a simple question regarding omniORBpy 2.0-beta2, that I downloaded
yesturday, and the versioning strategy.

The release notes of omniORBpy says that the archive should be expanded into
the src/lib directory of the omniORB source tree and we are wondering if
there is a way to have completely two different trees for omniORBpy and
omniORB so that can minimize dependancies between the two.
Also we were wondering how omniORBpy developers were handling versions
during the development, basically src/lib/omniORBpy is tagged
"omnipy2_develop", which tag is used for dependent libraries in bin
(omniORB400_rt.dll and omnithread30_rt.dll)?

Also in the case of one source directory how will be handled versioning in
the futur?
For example let's imagine that a fix goes into one of the public templates
of omniORB, will it require a recompilation of omniORBpy?

Arnault.
--

Arnault Bonafos	               SE II
Tumbleweed    Communications    Corp.
ph: (650) 216-2027  fx: (650) 216-2003