On Tue, Nov 20, 2007 at 03:17:41PM +0000, Ron Johnson wrote:
> On 11/20/07 03:00, Pierre Habouzit wrote:
> > Package: wnpp
> > Severity: wishlist
> > Owner: Pierre Habouzit <madcoder@debian.org>
> >
> > * Package name : tokyo-cabinet
> > Version : 1.0.6
> > Upstream Author : Mikio Hirabayashi <mikio@users.sourceforge.net>
> > * URL : http://tokyocabinet.sourceforge.net/
> > * License : LGPL
> > Programming Lang: C (with perl, ruby and java bindings)
> > Description : Tokyo Cabinet Database format [successor of QDBM]
> > Tokyo Cabinet is a library of routines for managing a database. The
> > database is a simple data file containing records, each is a pair of
> > a key and a value. Every key and value is serial bytes with variable
> > length. Both binary data and character string can be used as a key
> > and a value. There is neither concept of data tables nor data types.
> > Records are organized in hash table or B+ tree.
> > .
> > This library is presented as the successor of QDBM from the same
> > author.
>
> Should the source package create separate bindings packages for each
> language? That's standard, isn't it?
1) It's an ITP so it describes the _source_ package, not the split
I'll obviously perform.
2) it happens that unlike qdbm the bindings are separated upstream,
and as I've absolutely no interest in the bindings but only in the
C library I won't package them after all.
FWIW it's already in new, and there is 5 binary packages:
* the lib,
* the -dev package,
* the -dbg package,
* the -doc package,
* the -bin package with the tools to load/dump/... tokyocabinet
databases.
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
Attachment:
pgpjuVWgr0kKe.pgp
Description: PGP signature