Hi Jorge,
On Fri, Jan 10, 2014 at 10:41:58AM +0000, Jorge Sebastião Soares wrote:
> > 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... :)Well, that's a shame (see below ;-))
> We made the decision to create 3 debian packages for the snp_sites codeFine.
> instead of one monolythic package:
>
> [1] snp-sites - binaries
> [2] libsnp-sites1 - run time libraries
> [3] libsnp-sites1-dev - development libraries
No! have you seen any lib*.install files in the volpack example??
> Doing this means that we need to have .install files for the three packages:
>
> snp-sites.install
> libsnp-sites1.install
> libsnp-sites1-dev.install
D-shlibs is caring for installing the lib files and thus you can get rid
of these install files (which is part of the deal why d-shlibs is
comfortable and I was suggesting using it).
> libsnp-sites1.install is responsible for moving anything that gets put inTo make the story short I took the slight exercise at noon to
>
> usr/lib/*/
>
> to
>
> usr/lib/*/
>
> So in my understanding, this is the package that will install
> libsnp-sites.so1.0.0 and create the libsnp-sites.so symlink.
add d-shlibs to snp-sites. Please `git pull` and try to understand
every single change. If you do not understand just ask.
BTW, I noticed that your (now vanished) libsnp-sites1-dev.install was
brocken and did create separate directories for evary single header
file! The correct thing to do would have been
usr/share/*.h usr/include/snp-sites
Moreover - from an upstream point of view: what should do include files
in /usr/share????
Just trust d-shlibmove - it simply does the right thing without making
> Now libsnp-sites.so1.0.0 is definitely a run time library and from my
> understanding should belong to [2]. But maybe it should all belong to [3]
> and there would be no need for [2].
you to care for the specifics (at least in simple cases like this).
There is never any need - you can always try to implement the Debian
> If this is right, then there wouldn't even be a need to use d-shlibs.
Library policy ... if you know it by heart. ;-)
Hope the commit explained what I mean
> Can you shed some light on this when you have time.