Shared library packaging question

["Wuttke, Joachim" <j.wuttke@fz-juelich.de>]

Dear specialists,

I need more help.  Specifically, I am going to ask 3 questions.

My debian directory is still messed up, as it has been from the beginning:
either the automatic scripts are not ready to assist in generating a shared-library
package, or I used them in wrong way.

Here my control file :

---------------------------------------------------------------------------------------------------------------
Source: lmfit
Priority: extra
Maintainer: Joachim Wuttke <j.wuttke@fz-juelich.de>
Build-Depends: debhelper (>= 7), autotools-dev
Standards-Version: 3.8.4
Section: libs
Homepage: http://messen-und-deuten.de/lmfit/lmfit.html

Package: lmfit-dev
Section: libdevel
Architecture: any
Depends: lmfit (= ${binary:Version}), ${misc:Depends}
Description: Development files for Levenberg-Marquardt library lmfit
 A self-contained implementation of the Levenberg-Marquardt algorithm.
 Routine lmmin determines a parameter vector p that minimizes the Euclidean
 norm of a vectorial function v(p). The most important application is curve
 fitting: to approximate data y(t) by a function f(t;p), routine lmfit
 minimizes the norm of the residual vector v = y(t) - f(t;p).
 .
 This package contains the include file lmmin.h and some application examples.

Package: lmfit3
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: Least-squares minimization and curve fitting
 A self-contained implementation of the Levenberg-Marquardt algorithm.
 Routine lmmin determines a parameter vector p that minimizes the Euclidean
 norm of a vectorial function v(p). The most important application is curve
 fitting: to approximate data y(t) by a function f(t;p), routine lmfit
 minimizes the norm of the residual vector v = y(t) - f(t;p).
 .
 This package contains the shared library and the man page lmfit(3).
---------------------------------------------------------------------------------------------------------------

Stanislav suggested I create an additional doc package. Given the small
size of the entire project, I tend to think it's better not to inflate the packaging
overhead and to leave the examples in the dev package.

Question 1:
Is that permissible, or absolutely forbidden by some rule ?

Stanislav suggested the package name lmfit0. By now, however,
I succeeded in instructing autotools to generate the correct shared
library version number so.3.0.2; therefore, it's lmfit3.

Now I need to hand-edit the install files.

Seems straightforward for lmfit3.install:

---------------------------------------------------------------------------------------------------------------
usr/lib/lib*.a
usr/lib/lib*.so
usr/lib/*.la
---------------------------------------------------------------------------------------------------------------

Less trivially, lmfit-dev.install should install the following:

lib/lmmin.h   to   prefix/include/lmmin.h
doc/lmfit.3   to   prefix/share/man/man3
demo/*   to   ?

Question 2:
Where should the demo sources be installed to ?

Question 3:
Is it possible to write an install file such that the source directory
(e.g. "lib") is different from the destination directory ("include") ?
Or do I need to first reorganize my source directories ?

Thanks in advance, Joachim

------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzende des Aufsichtsrats: MinDir'in Baerbel Brumme-Bothe
Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
Dr. Ulrich Krafft (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------