[Pkg-ace-devel] Upload of ACE+TAO 6.0.3+2.0.3 to experimental

[Johnny Willemsen]

Hi,

> Patch format was changed to DEP3 to ease tracking; that's a first
> version that probably needs headers update.
> 
> Patches can be seen here:
> 
> http://anonscm.debian.org/gitweb/?p=pkg-ace/pkg-ace.git;a=tree;f=debian/patches;h=da6a20626bfcbafe3fc97d25c42ddc20790d16d8;hb=master
> 
> @Johnny: the following changes could be integrated in DOC repo:
> 
>  - 16-ace-inet-pkgconfig-files.diff, to create .pc files for the
>    ACE_INet library

Done, also the removal of ace_man.doxygen has been merged to head

>  - after compilation some files remain after a distclean, see:
> 
> http://anonscm.debian.org/gitweb/?p=pkg-ace/pkg-ace.git;a=blob;f=debian/TOREMOVE;h=b2ceb242f5aa289a02be1b46424108ca265a9a9c;hb=master

That probably is caused by some issues in our IDL dependency rules. This
should be fixed in the MPC files, or maybe something is wrong in
TAO/MPC/taobaseidldefaults.mpb

>  * investigate whether ACE or the packaging, could benefit using a
>    better versionning mechanism {?}.
>    Indeed for every release we have to go to NEW because the library
>    SONAME changes. How far is ACE+TAO from a stable API? This should be
>    discussed with upstream, but I think measuring diff for past release
>    may help. I see two different tools that could help here:
>      - dpkg symbol files [4]
>      - abi-compliance-checker [5]

We don't give any API guarantee between versions. For example the next
TAO version will have changes in it generated code which will change its
ABI compared to previous versions. I think there is no other option than
to go to NEW each time.

Johnny