Automatically probe for library location

[grr]

Previously requested 12 years ago: https://rt.cpan.org/Public/Bug/Display.html?id=70277

Use ExtUtils::PkgConfig, Devel::CheckLib, etc. to probe for the location of BerkeleyDB inc/lib locations.

[rjbs]

@pmqs It looks like you're at least kinda active. If I had a patch to make this work, would you apply and ship it?

[pmqs]

@pmqs It looks like you're at least kinda active. If I had a patch to make this work, would you apply and ship it?

Hey @rjbs

Crikey, I didn't think anyone was still using this code!

In principle I have no problem with a patch.

A few things to be aware of

• the current build supports really old versions of the Berkeley DB library.

  Probably ok for you to ignore this as long as the existing configuration process is still available.

• the other thing that used to happen quite frequently is where someone had multiple versions of the Berkeley DB library on their system and would try to build the code with version "A" of db.h and version "B" of the library. Then bad things would happen.

  Do the automated configuration toolsets cope with this scenario?

As long as the option is still available to use the crusty manual method I've put in place I image it should be ok.

[rjbs]

I don't actually use it, but wanted to try out some "serve pod as a web page" thing for potential internal use, and it relies on this, and "there's almost a patch to make it go" felt like maybe worth pursuing… :)

[pmqs]

I don't actually use it, but wanted to try out some "serve pod as a web page" thing for potential internal use, and it relies on this, and "there's almost a patch to make it go" felt like maybe worth pursuing… :)

Go for it!