Hi,
Thanks for your email. I am also interested in this, but I am unable to
pull code from the pkg-ace debian git repository. Nothing changed at my
side but I now get a public key error. I know all the details of
ACE/TAO, but the debian packaging guidelines are completely new to me. I
just don't have time to sort these all out myself.
Upstream we are able to compile ACE/TAO for OpenSuSE Build service for
Debian (see
http://download.opensuse.org/repositories/devel:/libraries:/ACE:/micro/Debian_7.0/).
As part of the ACE/TAO distribution you will find a debian directory
with the files I used for that, the files are automatically renamed with
each release.
If you have suggestions for improving the debian files as part of trunk
(see
https://svn.dre.vanderbilt.edu/viewvc/Middleware/trunk/ACE/debian/), let
me know, I can also easily update the files on opensuse build service to
try it out.
Most ideally would be that when I package a new ACE/TAO upstream release
I can also take some steps to upload the new release to debian, just as
I now upload all packages to Vanderbilt and to OpenSuSE build.
Regards,
Johnny
On 06/11/2014 08:28 PM, Barak A. Pearlmutter wrote:
As the Debian ivtools maintainer, I'd be interested in helping to solve
this. I did an NMU of ace in October to recompile with a new toolchain,
to keep ivtools happy.
It now appears that more is needed. I'd be happy to help, even to
co-maintain a bit if the ACE maintainer so desires.
But the packaging does look pretty complicated. The upstream build
system is MPC, so there's that learning curve. The debian/rules file is
not making full use of the more recent debhelper facilities, but it's
not clear to me that updating it in this fashion would really help with
keeping the package up to date. Something that automatically pulled
lists of files from the upstream build system (using executable
debian/*.install files, say) might make it easier to automatically
adjust to modified files in the installation, rather than having to do a
laborious reactive manual process per debian/README.source
Upstream assistance in doing things to make this easier to package, and
in making suggestions for adjusting the packaging for a better impedance
matching with the build system, might help a lot. E.g., are all the
little separate library packages (72 of them) necessary, or should some
of them be merged? Naturally things that make this easier to package
for Debian would probably also make it easier in other systems, like
Redhat.
Thoughts?
--Barak.
--
Barak A. Pearlmutter
Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
http://www.bcl.hamilton.ie/~barak/
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
