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

Thomas Girard thomas.g.girard at free.fr
Thu Oct 18 11:46:49 UTC 2007


>  * 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.

>  * fix #42953 by introducing libomni*-dbg packages. Since we're changing
>    names the package will go through NEW anyway.

done, using your changes to debian/control and dh_strip. Packages are
compiled with `-g -O2', then debugging symbols are moved into -dbg

One thing that would be nice is to handle DEB_BUILD_OPTIONS=noopt
(nostrip is already handled by dh_strip).

>  * Check the API from 4.0.6 to 4.1.0 to see if a new souce package
>    name is required.

I'll followup on this issue on #430422.

>  * test transition from omniorb 4.0 to omniorb 4.1:
>    o by hand
>    o with piuparts
>    o with an non-empty omniName database while updating to see if
>      registered objects are still there after
> Earlier I thought this was a lost cause due to the old postrm script,
> however I just re-read the policy and we'll have to write a preinst
> script which can handle this. 

I've tested transition by hand from 4.0 to 4.1 while testing for
omnievents compilation, and it went well.



More information about the Pkg-corba-devel mailing list