summaryrefslogtreecommitdiff
path: root/databases/db
AgeCommit message (Collapse)AuthorFilesLines
2005-03-15Avoid build failures under NetBSD-sparc and NetBSD-sparc64 caused by atron3-3/+17
namespace violation (use of "__" prefix in an application header file). The patch was provided by Julian Coleman in PR pkg/23590.
2005-02-27make this work on (even older) IRIX: check for __sgi rather than sgijschauma2-1/+15
This was originally reported in PR 28819 by Georg Schwarz for db4 and also noted by Georg to apply to this package.
2005-02-23Add RMD160 digests in addition to SHA1 ones.agc1-1/+2
2004-11-15Rework the Berkeley DB detection in buildlink3:jlam1-6/+5
* Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv2-3/+4
in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include.
2004-09-22Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.jlam1-5/+1
All library names listed by *.la files no longer need to be listed in the PLIST, e.g., instead of: lib/libfoo.a lib/libfoo.la lib/libfoo.so lib/libfoo.so.0 lib/libfoo.so.0.1 one simply needs: lib/libfoo.la and bsd.pkg.mk will automatically ensure that the additional library names are listed in the installed package +CONTENTS file. Also make LIBTOOLIZE_PLIST default to "yes".
2004-08-27Replace RPATH_FLAG with LINKER_RPATH_FLAG and COMPILER_RPATH_FLAG,jlam1-2/+2
which are the full option names used to set rpath directives for the linker and the compiler, respectively. In places were we are invoking the linker, use "${LINKER_RPATH_FLAG} <path>", where the space is inserted in case the flag is a word, e.g. -rpath. The default values of *_RPATH_FLAG are set by the compiler/*.mk files, depending on the compiler that you use. They may be overridden on a ${OPSYS}-specific basis by setting _OPSYS_LINKER_RPATH_FLAG and _OPSYS_COMPILER_RPATH_FLAG, respectively. Garbage-collect _OPSYS_RPATH_NAME and _COMPILER_LD_FLAG.
2004-07-10provide BUILDLINK_CPPFLAGS, LDFLAGS and LIBS for each pkgsrc dbgrant1-1/+4
implementation.
2004-07-07Set BUILDLINK_LIBDIRS.db?, as mail/exim expects.wiz1-1/+2
2004-07-06Unused.wiz1-60/+0
2004-05-26Use CFLAGS when creating the archive. This fixes building under IRIX64jschauma2-4/+4
using gcc, as we need the ABI specific flags.
2004-05-17Garbage collect BUILDLINK_PKGBASE.<pkg> from buildlink3: it is not anymoreseb1-2/+1
used since revision 1.139 of mk/buildlink3/bsd.buildlink3.mk.
2004-03-18Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properlyjlam1-7/+5
by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-16If the ${PKGBASE} of a package doesn't match the token passed tojlam1-1/+2
BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
2004-03-10bdb.buildlink3.mk is used to select a Berkeley DB implementation forjlam1-37/+15
use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-02-06If we're passing through MAKEFLAGS variables whose values may containjlam1-2/+2
spaces, use the :Q modifier instead of double-quoting the value. This avoids breakage when executing the just-in-time su targets.
2004-02-05Make PREFER_PKGSRC just yes/no or a list of packages. This makes itjlam2-10/+8
simpler to understand.
2004-02-05Rename BUILDLINK_PREFER_PKGSRC to PREFER_PKGSRC so that we can use itsjlam2-10/+8
value outside of buildlink-related files.
2004-02-05Support a new global variable:jlam2-2/+18
BUILDLINK_PREFER_PKGSRC This variable determines whether or not to prefer the pkgsrc versions of software that is also present in the base system. This variable is multi-state: defined, or "yes" always prefer the pkgsrc versions not defined, or "no" only use the pkgsrc versions if needed by dependency requirements This can also take a list of packages for which to prefer the pkgsrc-installed software. The package names may be found by consulting the value added to BUILDLINK_PACKAGES in the buildlink[23].mk files for that package.
2004-01-24Support BUILDLINK_DEPENDS.<pkg> being a list of values.jlam1-2/+2
2004-01-22avoid tickling a bmake bug.grant1-3/+5
2004-01-20Move WRKSRC definition away from the first paragraph in a Makefile.agc1-2/+2
2004-01-05bl3ifyjlam1-2/+6
2004-01-05Use S/+$// instead of C/\+$// to save a backslash. Very highlyjlam1-2/+2
recommended by seb :)
2004-01-05Sow BUILDLINK_USE_BUILTIN.<pkg> and reap _NEED_<PKG> variables.jlam1-12/+10
2004-01-04Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk.jlam1-4/+4
2004-01-03Initial sprinkling of work-in-progress buildlink3.mk files for using thejlam1-0/+41
buildlink3 framework.
2004-01-01Look inside db.h if it belongs to db3 or db4 (as it does on somewiz1-1/+7
Linux distributions). Based on a patch by Min Sik Kim in PR 23944.
2003-12-04+=, not =grant1-2/+2
2003-12-04provide BUILDLINK_LDFLAGS.db and BUILDLINK_LIBS.db.grant1-1/+7
2003-12-04USE_GNU_TOOLS=awk. fixes build on Solarisgrant1-1/+3
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-03-29Place WRKSRC where it belongs, to make pkglint happy; ok'ed by wiz.jmmv1-3/+2
2003-01-09Define NO_PKGTOOLS_REQD_CHECK, which will mean something in a moment.schmonz1-1/+3
2002-12-29Workaround an apparent bug in make (cannot put comment in a .eli* line).seb1-2/+3
2002-12-22Darwin, like NetBSD, has /usr/include/db.h.grant1-2/+2
2002-12-15If USE_DB185 is _not_ defined we actually want db2: introduce _NEED_DB2seb1-4/+10
to help sort this out.
2002-11-19Correct package list to match recent changes.tron1-1/+14
2002-11-18Allow this file to be used to mean "we want DB-1.85" if the inclusion ofjlam1-7/+22
this file is preceded by defining "USE_DB185". On NetBSD (and probably Linux), where we already have DB-1.85 in the base system, this defaults to using the system libraries and headers.
2002-11-18Always build the db-1.85-compatibility code, not just for Solaris. Bumpjlam1-7/+3
PKGREVISION.
2002-11-18Sort.jlam1-20/+7
2002-11-02update MASTER_SITES.grant1-2/+2
2002-10-10Unused.jlam1-34/+0
2002-09-26Add BUILDLINK_CPPFLAGS.<pkg> for these packages to help packages findjlam1-1/+3
the db[23] headers.
2002-08-25Merge changes in packages from the buildlink2 branch that havejlam3-7/+29
buildlink2.mk files back into the main trunk. This provides sufficient buildlink2 infrastructure to start merging other packages from the buildlink2 branch that have already been converted to use the buildlink2 framework.
2002-06-26Substitute a couple of `mkdir' by `${MKDIR}'.seb1-4/+4
Remove `-p' from mkdir arguments, it is already part of ${MKDIR}. While here substitute a couple of ${PREFIX} by `%D' in `@exec ${MKDIR} ...' lines and add a couple of missing `%D' in such lines too!
2002-02-15mkdir -> ${MKDIR}skrll1-4/+4
rmdir -> ${RMDIR} rm -> ${RM} (${RM} added to PLIST_SUBST) chmod -> ${CHMOD} chown -> ${CHOWN}
2001-11-01Move pkg/ files into package's toplevel directoryzuntum2-1/+1
2001-07-27Add dir_DEFAULT setting used by EVAL_PREFIX logic to set the defaultjlam1-1/+2
installation directory in case the package isn't installed.
2001-07-20Mechanical changes to buildlink.mk files to use EVAL_PREFIX to setjlam1-2/+2
BUILDLINK_PREFIX.<pkgname>. This allows buildlink to find X11BASE packages regardless of whether they were installed before or after xpkgwedge was installed. Idea by Alistair Crooks <agc@pkgsrc.org>.
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-01 16:05:48 +0000