[Pkg-ace-devel] 6.0.1

Pau Garcia i Quiles pgquiles at elpauer.org
Sat Feb 19 21:45:04 UTC 2011

On Fri, Feb 18, 2011 at 7:32 AM, Thomas Girard <thomas.g.girard at free.fr> wrote:

>>> What about adding libACE_INet package? Since we will have to go to NEW,
>>> it's better to add all new packages at once if we feel like we need
>>> them.
>> I'll try to look into that this weekend.


I have added the following packages:

* libace-inet-6.0.1, libace-inet-dev: ACE_INet
* libace-inet-ssl-6.0.1, libace-inet-ssl-dev: ACE_INet_SSL

I have also committed patch 16-ace-inet-pkgconfig-files, which are the
pkg-config files for ACE_INet and ACE_INet_SSL. It should be applied
upstream (Johnny?).

There is one detail I don't like about having ACE_INet and
ACE_INet_SSL in different packages: in ACE, the include files are not
split, all the header files are together in usr/include/ACE/INet. To
split them, I have looked for the files with include SSL or HTTPS in
the filename:

$ find . -type f | grep -vi https | grep -vi ssl  --> These go to

The ones matching HTTPS or SSL go in libace-inet-ssl-dev.install:

libace-inet-ssl-dev requires libace-inet-dev. I have checked and none
of the files I'm putting in libace-inet-dev include anything from
libace-inet-ssl-dev, therefore I think I'm not breaking anything:

$ find . -type f | grep -vi https | grep -vi ssl | xargs -I {} grep
-Hi "include.*ssl"

$ find . -type f | grep -vi https | grep -vi ssl | xargs -I {} grep
-Hi "include.*https"

(both return nothing)

Of course it would be much much easier if upstream put the header
files for ACE_INet into usr/include/ACE/INet and the header files for
ACE_INet_SSL into usr/include/ACE/INet/SSL or usr/include/ACE/INet_SSL

> Some other things that might be worth:
>  - switching to new 3.0 format + quilt

To silent lintian, I have stated explicitly we are using source format
1.0. I need to read more about 3.0 to know how to work with patches

>  - switching to git?

I have experimented a bit with this:

- I have converted the svn repository as of now to git following

- When importing upstream source, there were conflicts with upstream's
"debian" directory. I don't really know whether I should fix those
conflicts, or whether I should import-orig filtering out upstream's
"debian" directory ( git import-orig --filter=debian
../ACE+TAO+CIAO-src-6.0.1.tar.bz2 ). Stefano Zacchiroli suggested on
IRC I go with "--filter=debian" and convince upstream to not ship a
'debian' directory :-?

I have uploaded the result of filtering out upstream's "debian"
directory to http://www.elpauer.org/tmp/pkg-ace.git.tar.bz2 . Please
check it ("gitk --all" comes handy). If you think it's in good shape,
we can arrange a date and time for the final conversion (after 6.0.1-1
is released looks good to me). I would need you to create a git
repository (see http://wiki.debian.org/Alioth/FAQ#vcs-repos ), then
when the final conversion is done, I will push the converted git
repository (assuming I have the proper permissions in Alioth).

>  - any other idea

Maybe we could keep a README-RELEASE.txt or something like that with
notes of things to check for each release. For instance:

- Update patch 34-bts386713
- Regenerate the list of include files for libace-inet-dev and

Pau Garcia i Quiles
(Due to my workload, I may need 10 days to answer)

More information about the Pkg-ace-devel mailing list