Re: Bug#610603: ITP: sra-sdk -- utilities for the NCBI Sequence Read Archive

[Andreas Tille <andreas@an3as.eu>]

On Thu, Jan 20, 2011 at 09:15:43PM +0900, Charles Plessy wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Charles Plessy <plessy@debian.org>
> 
>   Package name    : sra-sdk

Thanks for the ITP.  I added it to the tasks file.
 
> I will first upload to experimental until a final release is published.
 
> I understand that having one package per library is ideal, but the
> number of different libaries is quite large:

I'm not absolutely sure that there is such a thing like "the" ideal
packaging.  I know that having more libraries in one package is
triggering lintian warnings - but sometimes it makes more sense to
collect them all in one package.
 
> /usr/lib/libwkdb.so.1.1.2
> /usr/lib/libkproc.so.1.0.0
> /usr/lib/libsra-schema.so.1.0.0
> /usr/lib/libvdb.so.2.0.4
> /usr/lib/libkq.so.1.0.0
> /usr/lib/libksrch.so.1.0.2
> /usr/lib/libkfs.so.1.0.2
> /usr/lib/libkdb.so.1.1.2
> /usr/lib/libwvdb.so.2.0.4
> /usr/lib/libksproc.so.1.0.0
> /usr/lib/libkfg.so.1.0.0
> /usr/lib/libkxml.so.1.0.2
> /usr/lib/libwsradb.so.3.0.1
> /usr/lib/libklib.so.1.1.0
> /usr/lib/libsrareader.so.1.0.0
> /usr/lib/libsradb.so.3.0.1
> 
> This said, if a more experienced developer would still recommend me to
> make one package per library, I will. I checked with upstream and
> these libraries are intended for public use (although given that they
> are recent, there is no known third-party using them yet).

I'd say go for it in one package and once we have a drastical raise
in popcon numbers which gives some evidence that users are keen on
using specific stuff we could change this later.

Kind regards

     Andreas.

-- 
http://fam-tille.de