Bug#748373: python-lmdb
On Thu, Dec 11, 2014 at 6:30 PM, Robert Edmonds <edmonds@debian.org> wrote:
> Hi,
>
> I'm planning on using py-lmdb for a project, and it appears no one else
> is working on a package, so I'll be happy to take this RFP.
>
> David Wilson wrote:
>> * The binding is still receiving significant development, so before any
>> particular version becomes frozen, please drop me an e-mail to ensure
>> the latest and greatest (and possibly stablest) release is available
>> prior to the freeze.
>
> As jessie is now frozen without a py-lmdb package in the archive, it
> won't be part of the next stable release. So you have a few more years
> before a particular version of py-lmdb becomes frozen :-)
pffh, who works with debian/stable anyway? :)
actually doing the packaging robert is very very straightforward, i
did it once (in a proprietary environment), i just followed the
standard python arrangement, i think the debian/rules file was about 7
or 8 lines long, absolutely nothing special whatsoever was needed.
the only thing is: david committed a copy of liblmdb into python-lmdb
- smacked wrist there david :) - it's statically compiled into
python-lmdb's lmdb.so and is very small...
... whilst this does have the advantage that the (closely-tied)
version of liblmdb to python-lmdb needs no further thought or work, if
you want to consider separating it so that there's a dependency on
liblmdb0, you're in for a bit of a mess as whatever stable version of
liblmdb0 is nailed to the floor, that's what you have to restrict
python-lmdb to.
honestly my advice, given that liblmdb is so small, would be to stick
to what david's done, for now, and once python-lmdb can be considered
stable in a few years time the situation can be revisited.
l.
Reply to: