[Pkg-corba-devel] omniORB status

Thomas Girard thomas.g.girard at free.fr
Wed Nov 28 20:08:34 UTC 2007

Hello Floris,

On Mon, Nov 26, 2007 at 07:35:35PM +0100, Thomas Girard wrote:
> > Noteworthy things that may require some more testing then I have done
> > with it so far are the fact that I decided to not patch the upstream
> > build as much, i.e. use omkdepend instead of gcc -M and use mkdirhier
> > instead of mkdir -p.  So far I have not seen a problem because of
> > these.
> > 
> > I also included the omkdepend binary in /usr/bin to close #277627 as I
> > don't really see any harm in that, although it is not clear if it is
> > actually needed anymore[1].  I'll need to write a manpage for it
> > though, which might be tricky as it doesn't even have a --help
> > option...
> I'm trying a rebuild right now. I'll let you know if it goes fine.

The build went fine. But if you agree we'll delay the omkdepend issue.
Indeed, I have (at last) found references[1][2][3] of a discussion between
the previous maintainer and upstream. It seems that by that time
omkdepend did not run on a few archs. Besides, I'm not sure it should be
included in omniorb4 package, which contains CORBA IOR tools only. (In
fact I have no idea where omkdepend should go.)

Given that we need omniORB >= 4.1.1 to upload omniEvents 2.6.2 and omniORBpy
3.1 I think this minor, yet to be solved, issue can wait.

How about that?


[1] http://www.omniorb-support.com/pipermail/omniorb-list/2002-October/022062.html
[2] http://www.omniorb-support.com/pipermail/omniorb-list/2002-November/022162.html
[3] http://www.omniorb-support.com/pipermail/omniorb-list/2002-November/022173.html

More information about the Pkg-corba-devel mailing list