[Pkg-ace-devel] Plan for ACE+TAO upload

Thomas Girard thomas.g.girard at free.fr
Mon May 3 19:25:33 UTC 2010


Le 03/05/2010 16:07, Johnny Willemsen a écrit :
> First, to my idea packaging should just be packaging, no patching to
> ACE/TAO files. If there are issues found with packaging they should be
> fixed the correct way on svn head.

Yes, we agree on that. I'll ask Eric to check why my account on the DOC
repo is not working. In the meantime, could you please review and
fast-track changes in the DOC repo?

> On 05/01/2010 03:47 PM, Thomas Girard wrote:
>> 1 Decide what to do with library naming, either:
>>       libWhatever-x.y.z.so; or
>>       libWhatever.so.x.y.z
>>
>>     Upstream uses the latter. But I would go for the former; see
>>     rationale in [1] that was applied for autoconf method and IMHO
>>     should be applied for traditional method as well.
>
> I prefer the last one

Could you please elaborate on that? The fact that the version x.y.z
follows the .so makes one think there is an ABI versioning being used,
while it's just a release version, with no backward compatibility.

>> 2 After that, teach ACE_DYNAMIC_SERVICE_DIRECTIVE to use versioned
>>     libraries the way we want.
> We should extend the macros with a version argument which is passed down
> from TAO

Ack.

>>    3 Shall we compile ACE+TAO with optimization level -O3 to follow
>>     upstream? Johnny, are you aware of problems because of this?
>
> Should work without problems

Ok.

>>    5 Discuss what we should do for the following features:
>>     - ipv6 (we used to have ipv6 and ipv4-ipv6 in 5.6.3)
> Shouldn't be a problem

Already enabled again.

>>     - uses_wchar
> We shouldn't do that, that is a completely different build

What would this bring us? What is the loss?

>>     - sctp
> Is stable for production, but enabling this will mean we add that
> dependency, do we want that?

Depends on the dependency I would say :-) Does this require a kernel
level dependency (which would be a no go), or only userspace library?
Can it be disabled at runtime, or only at compilation time?


>>     - gen_ostream
> Shouldn't do that, makes things bigger
>>     - notify_monitor_control
> Disable also
>>     - negotiate_codesets
> Also disable
>>     - ziparchive
> Disable
>>     - xerces3
> You can enable it, but only used for CIAO
>>     - ZIP_Wrapper
> Also for CIAO

Ok.

Thanks for your inputs,
Regards,

Thomas



More information about the Pkg-ace-devel mailing list