Re: py-bsddb3 (was Re: BAD Python compilation directives)

[Thomas Klausner <tk%giga.or.at@localhost>]

On Thu, Jan 26, 2017 at 04:25:12AM +0100, Jesus Cea wrote:
> Talking about this, my bindings, when compiled, link to the most recent
> version of Berkeley DB installed. Nevertheless, the pkgsrc packages:
> 
> """
> [root@eMail ~]# pkgin search bsddb
> py35-bsddb3-6.2.1    Python bindings for Oracle Berkeley DB
> py34-bsddb3-6.2.1    Python bindings for Oracle Berkeley DB
> py27-bsddb3-6.2.1    Python bindings for Oracle Berkeley DB
> """
> 
> link statically against Berkeley DB 4.8.30, even if I have 6.1
> installed.

mk/bdb.buildlink3.mk currently sets the default to db4 if no explicit
choice is made. The user can set BDB_DEFAULT=db6 in the mk.conf file,
then db6 will be used.

Perhaps it's time to bump the default to db6?

> Another question: last Berkeley DB available in pkgsrc is 6.1, but
> Oracle published 6.2 a year ago and I suppose it is going to publish 6.3
> sometime in 2017. Currently pkgsrc doesn't allow several versions
> installed at the same time because they could collide in
> "/opt/local/lib/libdb6.so" and other places. How could that be solved?.

Adam just updated db6 to 6.2.

Cheers,
 Thomas