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

Johnny Willemsen jwillemsen at remedy.nl
Mon May 3 14:07:05 UTC 2010


Hi,

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.

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

>   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

>   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
>    - uses_wchar
We shouldn't do that, that is a completely different build
>    - sctp
Is stable for production, but enabling this will mean we add that
dependency, do we want that?
>    - 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

Johnny
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jwillemsen.vcf
Type: text/x-vcard
Size: 309 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ace-devel/attachments/20100503/e917ed00/attachment.vcf>


More information about the Pkg-ace-devel mailing list