On Sun, May 18, 2003, Tassilo Erlewein wrote:
> I found that some packages' configure scripts fail to detect the
> openpkg libdb.
Really? Which particular packages? AFAIL we've already patched some
packages to correctly pick up our Berkeley-DB some time ago before
OpenPKG 1.2.
> The reason to me seems that you don't
> provide a lot of fancy named links to libdb.a.
That's correct. But IMHO those "fancy" names are nasty and I think we
should not play this game in OpenPKG, because it introduces mud into the
package. Instead, fixing or tweaking those packages which are unable to
find a straight-forward libdb.a should be fixed by us.
> Problem is that most unixes do so.
Linux Distros do it this way, yes. A clean system where you just have
a single version of Berkeley-DB for all packages usually do not want
those libfoo-VERSION.a stuff. In OpenPKG we went the hard way and fixed
many packages so they work with the latest Berkeley-DB 4.1 while the
Linux distros just go the lazy way and install multiple versions of
Berkeley-DB to avoid having to fix all their packages. We do not really
want this.
> At least the configure scripts
> of openldap, sasl and imapd match libdb.a as last, so the underlying
> system's libdb will "win" in most cases.
Good catch. I've tried to fix "openldap" in OpenPKG-CURRENT now, too.
"sasl" and "imapd" were already patched to pick up our Berkeley-DB
first.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
