On Fri, Feb 15, 2013 at 5:00 PM, Raphael Eiselstein <[email protected]> wrote: > Hi all, > > Just to get an answer to this thread: > > On Sat, Feb 09, 2013 at 02:13:30PM +0100, Raphael Eiselstein wrote: >> On Sat, Feb 09, 2013 at 01:51:09PM +0100, Herbert J. Skuhra wrote: >> > # <UNIQUENAME>_WITH_BDB_VER >> > in /etc/make.conf? >> havn't tried yet. But for me it makes more sens to pin all ports to the >> *same* version of BDB. > > I set WITH_BDB_HIGHEST=x in my /etc/make.conf of the build-jail. > *All* packages depending on db4x will be linked to db44 now, as this is > the highest version. > > I haven't test all binaries "in depth" but different build runds were fine > for the last couple of days and I didn't see any problems yet (libchk ...) > >> Is there any problem linking db44 to *any* port? > > I didn't see some, but ... ? > >> Why do we have so much versions of bdb in our ports? > > I guess there must be technical reasons for this. Can anyone explain? > Where are the differneces between db41, db42 and db44? Why not just > shipping db44 or higher? > The reason that there are so many BDB versions in ports is that several of the functions had additional arguments added or swapped between versions.
Some ports will require either: - patching to work with latest versions of BDB - upgrade to latest source version that works with the latest version of BDB -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
