[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Different versions between library and its supplied binary program



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

I'm packaging a library (harminv, which implements a method to solve
harmonic inversion problems) which supplies a program which makes use
of the library... According to the section 8.2 of Debian Policy, i've
to put the program into the -dev package, or in its own package.

The problem is that, at some point, mainstream author decided that
complete package version (library + program) is different than the
libraries version (which, as he tells, is an 'internal-use' version).
Library is actually 2.0.3, and the complete package is 1.3 (which is
the program version too). This makes lintian complain about it if i
package it as harminv1.3. My question is, what may i do?:

1) Make 3 packages: libharminv2.0.3, libharminv-dev, and harminv1.3,
this last only holding the program and its man page.
2) Make 2 packages, including harminv program into the -dev package.
3) Ignore lintian error, and provide harminv1.3 (shared libraries),
and harminv-dev (static libraries, header files and binary program).

What do you think is better?

Regards,
Roi Rodriguez
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEnxBF7//feQwW65kRAu8YAJ9aZgKIdH4osUM1OBcVPHq4MylFdwCcCo4j
qpa8yLUfcbPvVwTDnD1XP/A=
=nvTQ
-----END PGP SIGNATURE-----



Reply to: