Skip to content
Commits on Source (2)
Show whitespace changes
Inline Side-by-side
debian/README.source
View file @ e55a2044
......@@ -35,7 +35,7 @@ care about identifying local symbols for now.
About C++ symbols tracking
--------------------------
Tracking C++ versioned symbols is complacated:
Tracking C++ versioned symbols is complicated:
* Firstly we need to track them under their unmangled form to be arch
independant.
* Secondly I discovered after many /try fail repeat/ that dpkg-gensymbols
......@@ -45,6 +45,7 @@ Tracking C++ versioned symbols is complacated:
* Finaly the patches generated by dpkg-gensymbols don't allow any
comment in the symbols files and requires a specific sorting order
(bug #773718).
All these concerns are handled by three helper scripts:
* debian/process-symbols-files
* debian/sort-symbols
......@@ -57,32 +58,6 @@ using this C++ library, we didn't bother.
The script debian/check-dep-on-hdf5-cpp is used to check these dependencies.
About shared libraries versioning and SONAME
--------------------------------------------
Worth reading to get the picture about libtool versioning:
<http://bzed.de/scratchpad/soname-libtool.txt>
[Old note - for the record]
> About versioning style. In very recent times (since 1.8 series) HDF Group
> introduced a libtool SONAME versioning in the library with major/minor releases.
> Unfortunately, past experieces showed that API retention has been sometimes
> violated in the past, so current packages use a defensive approach by considering
> each release as not back-compatible. This is also motivated by the presence of
> of C++ and Fortran bindings as well as multiple MPI editions, which could imply
> ABI breakages even for minor releases. Be defensive is more safe, definitively
Looking at the 1.8.x releases, it seems that upstream doesn't apply the
libtool versioning strategy. Instead they use it the major.medium.minor way
where:
* medium=0
* minor++ on release
* major++, minor=0 on API breaks
Considering applying this piece of advice from Julien Cristau:
> J'aurais tendance à suggérer d'utiliser le switch -version-number de
> libtool plutôt que -version-info. Ça prend directement comme argument
> major:minor:micro, donc on se perd pas dans des calculs à la con.
Manpages
--------
$ help2man -n "helper script to compile HDF5 Fortran applications" --version-string="h5pfc (hdf5 1.8.12)" -h -help -N h5pfc >debian/man/h5pfc.1
......@@ -92,9 +67,6 @@ $ help2man -n "debugs an existing HDF5 file at a low level" --version-string="h5
TO-DO
-----
* common manpage for h5*{c,f}c
* patch libtool usage to use -version-number instead of -version-info'?
* propose to upstream to use a separate libtool version for each language
(C, C++, Fortran)?
-- Francesco Paolo Lovergine <frankie@debian.org> Mon Jan 25 06:00:00 CET 2010
-- Gilles Filippini <pini@debian.org> Mon, 22 Dec 2014 01:50:39 +0100
-- Gilles Filippini <pini@debian.org> Wed, 10 Apr 2019 13:19:06 +0200
debian/changelog
View file @ e55a2044
hdf5 (1.10.5+repack-1~exp4) experimental; urgency=medium
* Add missing dependencies to libhdf5-{mpich,openmpi}-dev (closes:
#927446)
* Update debian/README.source
-- Gilles Filippini <pini@debian.org> Sat, 20 Apr 2019 18:26:40 +0200
hdf5 (1.10.5+repack-1~exp3) experimental; urgency=medium
* Add C++ and HL C++ runtimes for parallel flavors (unsupported
......
debian/control
View file @ e55a2044
......@@ -256,6 +256,8 @@ Depends: libhdf5-openmpi-103 (= ${binary:Version}),
libhdf5-openmpi-fortran-102 (= ${binary:Version}),
libhdf5-openmpi-hl-100 (= ${binary:Version}),
libhdf5-openmpi-hl-fortran-100 (= ${binary:Version}),
libhdf5-openmpi-cpp-103 (= ${binary:Version}),
libhdf5-openmpi-hl-cpp-100 (= ${binary:Version}),
zlib1g-dev,
libaec-dev,
libjpeg-dev,
......@@ -380,6 +382,8 @@ Depends: libhdf5-mpich-103 (= ${binary:Version}),
libhdf5-mpich-fortran-102 (= ${binary:Version}),
libhdf5-mpich-hl-100 (= ${binary:Version}),
libhdf5-mpich-hl-fortran-100 (= ${binary:Version}),
libhdf5-mpich-cpp-103 (= ${binary:Version}),
libhdf5-mpich-hl-cpp-100 (= ${binary:Version}),
zlib1g-dev,
libaec-dev,
libjpeg-dev,
......
debian/control.in
View file @ e55a2044
......@@ -256,6 +256,8 @@ Depends: libhdf5-openmpi-@SONAME@ (= ${binary:Version}),
libhdf5-openmpi-fortran-@SONAME_F@ (= ${binary:Version}),
libhdf5-openmpi-hl-@SONAME_HL@ (= ${binary:Version}),
libhdf5-openmpi-hl-fortran-@SONAME_HL_F@ (= ${binary:Version}),
libhdf5-openmpi-cpp-@SONAME_CXX@ (= ${binary:Version}),
libhdf5-openmpi-hl-cpp-@SONAME_HL_CXX@ (= ${binary:Version}),
zlib1g-dev,
libaec-dev,
libjpeg-dev,
......@@ -380,6 +382,8 @@ Depends: libhdf5-mpich-@SONAME@ (= ${binary:Version}),
libhdf5-mpich-fortran-@SONAME_F@ (= ${binary:Version}),
libhdf5-mpich-hl-@SONAME_HL@ (= ${binary:Version}),
libhdf5-mpich-hl-fortran-@SONAME_HL_F@ (= ${binary:Version}),
libhdf5-mpich-cpp-@SONAME_CXX@ (= ${binary:Version}),
libhdf5-mpich-hl-cpp-@SONAME_HL_CXX@ (= ${binary:Version}),
zlib1g-dev,
libaec-dev,
libjpeg-dev,
......