Hi Andreas,
Pasting here issues discussed on th eother thread:
> No. Lintian tells you exactly what you need to do. *Since* you are
> using compat level 9 you really *need* to bump also the versioned
> Build-Depends to 9 (currently you have 8). This is not the kind of
> warning you should override at all.
This was easy to do and is sorted.
> Creating library packages is a bit more advanced task. Since you have
> decided to be brave and created these you should finish the hard way,
> thought.
I start to regret it... :)
> I really like to use d-shlibs which is implementing the Debian
> Library packaging guide automatically. The expense you have to pay is
> to learn how to deal with d-shlibs and its pickyness to some extend.
> IMHO the easiest way is to copy some example and I'd recommend for
> instance
>
> svn://
anonscm.debian.org/debian-med/trunk/packages/volpack/trunk/Got this.
>
> You should have a look into its rules file and its control file.
> D-shlibmove will tell you everything else you need to do - if it is
> not verbose enough for you feel free to keep on asking.
>
> For sure you can move around the files manually without d-shlibs but the
> *.a file needs to go to the *-dev package as well as the *.so symlink.
I spent yesterday trying to understand how I could use d-shlibs to deal with the lintian warning:
W: libsnp-sites1: non-dev-pkg-with-shlib-symlink usr/lib/x86_64-linux-gnu/libsnp-sites.so.1.0.0 usr/lib/x86_64-linux-gnu/libsnp-sites.so
I didn't get very far TBH. So I would like to ask you a couple of questions, to see if I can get a clearer picture.
We made the decision to create 3 debian packages for the snp_sites code instead of one monolythic package: