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

[Thomas Girard]

Le 01/08/2011 09:52, Johnny Willemsen a écrit :
>> @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 

Thanks.

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

Okay. Let's add this to the TODO list :-)

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

I know there's no guarantee for now. I believe this could be useful for
customers too; for examples switching to a new ACE+TAO release would
require no recompilation or change. This could be a separate ACE+TAO
long term support branch, or something else. We could use Debian
packages for proof-of-concept. This could lead to redefining the
meaning of BFO releases. Anyway, I think it's worth discussing.

Before bringing this topic on devo-group@ I'd like to gather data using
past releases, e.g. 6.0.0 to 6.0.3 to get an idea of what changes
between releases.

Regards,

Thomas