Bug#748373: python-lmdb
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 :-) -- Robert Edmonds edmo...@debian.org -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141211173049.ga19...@mycre.ws
Bug#748373: python-lmdb
On Thu, Dec 11, 2014 at 6:30 PM, Robert Edmonds edmo...@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. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/capweedyao66esmq1dotf4lvowmzyofrct_buoapo4xidfpq...@mail.gmail.com
Bug#748373: python-lmdb
Just a small note - while I am the author of LMDB, I am not the author of py-lmdb. That's David Wilson. But we do keep in close contact... -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/ -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5378a744.6030...@symas.com
Bug#748373: python-lmdb
This is just to note a few minor complications if this gets packaged: * By default it links its own private LMDB, but this is easily changed (see documentation) * 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. Currently I release approximately monthly, slightly preferring freshness over stability, and the existing QA process is very basic. * The binding comes in two variants. For Debian it seems the CPython extension module will always be used, however this becomes more complicated if a Debian-packaged version of PyPy ever wanted to share the same python-lmdb package. So there is possibly quite a bit of wrangling around how the package would be built, perhaps some changes to the package itself to support the cohabitation, and additionally how to avoid the libffi/cffi dependency when just the CPython extension is in use. David -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140518230347.GA15898@k2
