[Pkg-corba-devel] Fwd: Remaining issues before uploading omniORB 4.1

[Floris Bruynooghe]

Oops, resending to the list.

---------- Forwarded message ----------
From: Floris Bruynooghe <floris.bruynooghe at gmail.com>
Date: 10 Nov 2007 19:07
Subject: Re: [Pkg-corba-devel] Remaining issues before uploading omniORB 4.1
To: Thomas Girard <thomas.g.girard at free.fr>


On 18/10/2007, Thomas Girard <thomas.g.girard at free.fr> wrote:
> >  * see if the just released 4.1.1 is ABI compatible with 4.1. If it's
> >    not, we'd better focus on the latest release.
>
> It is. The API/ABI changes I've seen only affect omniORB4/internal/
> headers, and I was about to remove them from libomniorb4-dev...
>
> >  * see if omnievents compiles fine with omniORB 4.1. (See with Martin.)
>
> ... when I noticed omnievents uses an internal header: orbOptions.h. For
> now let's leave this file in the -dev package: omnievents builds fine
> with it.

But python-omniorb2 doesn't.  It seems to use a
-I/usr/include/omniORB4/internal switch to gcc to so it didn't show up
in a grep, only when I tried to compile it I noticed.

I'm tempted to include all the internal headers again and yet claim it
is still API compatible since they are not part of the outside API
anyway.

Any objections?

Regards
Floris

--
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org