Date: Thu, 06 Nov 2003 16:51:59 +0100 From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de> To: freebsd-ports@freebsd.org Subject: Re: RFC: FreeBSD DB Port Reform Message-ID: <m3brrpo5pc.fsf@merlin.emma.line.org> In-Reply-To: <20031106153142.GA829@chetwood.ru> (Sergei Kolobov's message of "Thu, 6 Nov 2003 18:31:42 %2B0300") References: <m365hxoh65.fsf@merlin.emma.line.org> <3FAA3B77.7090002@fillmore-labs.com> <20031106141924.GA11241@merlin.emma.line.org> <20031106153142.GA829@chetwood.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Sergei Kolobov <sergei@freebsd.org> writes:
> How about this instead,:
>
> CPPFLAGS+= -I${LOCALBASE}/include/db${BDB_VER}
> LDFLAGS+= -L${LOCALBASE}/lib/db{BDB_VER}
> CONFIGURE_ENV+= CPPFLAGS="${CPPFLAGS}" LDFLAGS="${LDFLAGS}"
>
> That way, third-party apps will link against -ldb,
> and no patching will be required.
That will still require patches to a lot of ports (or their configure
scripts, respectively), many have magic to derive the library path from
the include path or assume they can get $COMMON_BERKELEYDB_LOCATION/bin
and $COMMON_BERKELEYDB_LOCATION/lib with the same prefix, --with-db= is
common.
These assumptions are met by existing Linux systems or manual BerkeleyDB
installs (that use the taunted /usr/local/BerkeleyDB.MAJOR.MINOR
layout), but we'll still break them with a lib/db*/libdb* layout.
We can't hope to simplify ports if we continue to break their build-time
assumptions, and I'd prefer to make such intrusive changes (that require
ports to be updated) in one single round and not today (to meet hier(7))
If hier(7) is so off-limits/intangible that we cannot leave a
/usr/local/$PORTNAME in addition to the usual stuff, we'll have to
continue patching the ports.
One way to avoid the BerkeleyDB.N.M directories altogether would be
either linking the then-current version, 4.1 at this time, to the
libdb-4.so and libdb.so files, and require that ports that use older
versions be patched, but I suspect we'll see a lot of trouble then from
people who assume that libdb-4 is libdb-4.0 rather than libdb-4.1. If
the path codes the version, this is less likely.
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m3brrpo5pc.fsf>