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

[Thomas Girard]

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

I'm not sure changing the source package name is needed. I've suggested
this, but since we will not support omniorb 4.0 and 4.1 I don't see the
need for a new source package name. I'll check in the Policy. 

Completely unrelated: I'm wondering whether omniNames manual page
section should be 8 or 1.

> >  * 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.
> 
> I hope it is as I'd prefer to get 4.1.0 in the archive first.  I
> suppose you want to avoid having to go through NEW twice? 

I'd prefer that too. (Yes, avoiding another stay in NEW would be
better.)

> >  * fix #42953 by introducing libomni*-dbg packages. Since we're changing
> >    names the package will go through NEW anyway.
> 
> This is moderately messy due to the way omniORB does it's build.  But
> I have done something similar at work (not Debian packages though) and
> have a hackish way of doing it (involving sed...).  I'll adapt it for
> the Debian package and try to upload it this week. 

The attached patch (uncommitted) adds `-g' using CC and CXX configure
variables. If you're fine with it I'll commit it and create missing
-dbg packages.

> > What do you think?
> 
> Yes, that seems about right.  Are you in any hurry?  I am fairly busy
> the next few weeks as I'll be away all weekends so will have to do
> with the time I can find in the weeks to work on this. 

I'm not really in a hurry. Let's fix the remaining issues.

Thanks,

Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: omniorb4_with_debug.diff
Type: text/x-patch
Size: 1441 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-corba-devel/attachments/20071011/e51feab1/attachment.bin