summaryrefslogtreecommitdiff
path: root/databases
AgeCommit message (Collapse)AuthorFilesLines
2001-11-28Update p5-perl-ldap to 0.25; notable changes since 0.23 include:kleink2-5/+6
perl-ldap 0.25 29 Oct 2001 ========================== * Added support for EXTERNAL SASL authentication * Caller can now specify attributes to return from root_dse * More scripts added to contrib * Various bug fixes * Caller can now specify sslversion for LDAPS and start_tls perl-ldap 0.24 17 July 2001 =========================== * Added support for startTLS * Better error checking in Net::LDAP methods * VLV control now works * Can now use oid or name for the matchingRule in filter extensible matches * Major overhaul of LDIF.pm * $schema->name2oid is now context sensetive * test suite now works with openldap2
2001-11-28Update to 0.47, as this is needed by the newest RT. No up to datemjl2-5/+5
changes are available unfortunately.
2001-11-28Buildlinkify.jlam2-6/+9
2001-11-26Use PKG_{USERS,GROUPS} instead of PKG_{USER,GROUP}.jlam2-9/+8
2001-11-26Forgot a CONFDIR -> PKG_SYSCONFDIR replacement.jlam1-2/+2
2001-11-26Buildlinkify, in the sense that only the perl headers are found injlam15-44/+70
${PREFIX} -- everything else is pickup up from ${BUILDLINK_DIR}.
2001-11-25PKG_SYSCONFDIR is where the configuration files for a package may be found.jlam1-4/+4
This value may be customized in various ways: PKG_SYSCONFBASE is the main config directory under which all package configuration files are to be found. PKG_SYSCONFSUBDIR is the subdirectory of PKG_SYSCONFBASE under which the configuration files for a particular package may be found. PKG_SYSCONFDIR.${PKGBASE} overrides the value of ${PKG_SYSCONFDIR} for a particular package. Users will typically want to set PKG_SYSCONFBASE to /etc, or accept the default location of ${PREFIX}/etc. This obsoletes the use of CONFDIR, which was active for only 6 days, so no need to have a workaround to still accept old CONFDIR settings.
2001-11-22Use download sites suggested by Indrek Siitan by MySQL AB. This fixestron1-3/+3
PR pkg/14605 by Michael Richardson.
2001-11-21Use libtool to install programs that were linked with libtool.jlam2-7/+7
2001-11-21RCD_SCRIPTS now just lists the filenames (see bsd.pkg.install.mk).jlam1-2/+2
2001-11-19Note addition of databases/php4-odbc.jlam1-1/+2
2001-11-19databases/php4-odbc - PHP4 access to ODBC data sourcesjlam3-0/+20
2001-11-19Adapt to use shared INSTALL/DEINSTALL scripts by using the logic injlam8-335/+27
bsd.pkg.install.mk: * Remove old DEINSTALL/INSTALL scripts. * Move some text printed at POST-INSTALL time into the MESSAGE file. * Adjust rc.d scripts to respect rc.conf settings, so that the script may be directly copied into /etc/rc.d.
2001-11-19SQLite is now on version 2.1.1 incorporating many changes, enhancementsreinoud1-0/+1
and bugfixes including support for 16Mb rows. For a full change see the website's changelog at http://www.hwaci.com/sw/sqlite/changes.html The file format changed! so please dump the database in SQL with .dump in the old version and import it later in the new version.
2001-11-19Just noted that some important bugfixes were made to version 2.1.0 to makereinoud2-5/+5
version 2.1.1
2001-11-19Update SQLite package to version 2.1.0 from 2.0.5reinoud4-64/+14
2001-11-13* Strongly buildlinkify.jlam2-19/+19
2001-11-11Adjust format a bit:hubertf2-2/+10
* 75 * '=' * RCS ID * blank line * message text * optional blank line * 75 * '='
2001-11-07Workaround differences in "make" behaviour between 1.5.2 and -current.jlam1-1/+2
These packages use GNU-automake-generated Makefiles, so we can pass our ${MAKE_FLAGS} in through AM_MAKEFLAGS.
2001-11-06Note additions of:jlam1-1/+4
databases/unixodbc databases/unixodbc-DataManager databases/unixodbc-ODBCConfig
2001-11-06databases/unixodbc-DataManager:jlam5-0/+65
GUI tool for unixODBC data source management The ODBC Data Manager can be used to browse/explore ODBC Data Sources, to drill down a data source, or to edit and to submit SQL.
2001-11-06databases/unixodbc-ODBCConfig - GUI tool for unixODBC driver configurationjlam5-0/+80
The ODBC Config program is a graphical program used to make configuration of ODBC Data Sources extremely easy. It has been designed to be user- compatible with the Microsoft(R) ODBC Administrator.
2001-11-06databases/unixodbc - ODBC 2.x/3.x driver managerjlam10-0/+490
The unixODBC project provides UNIX applications with the same ODBC 3.51 API and facilities available under MS Windows. It provides a Driver Manager that supports the full ODBC API and performs the ODBC 3 to ODBC 2 translations with UNICODE to ANSI conversion. It also includes a collection of ODBC drivers including a simple text-based driver, an NNTP driver, a Postgres driver and others, and a selection of templates and libraries that to aid in the construction of ODBC drivers. It works with MySQL, Postgres, StarOffice, Applixware, iHTML, PHP, Perl DBD::ODBC, Paradox 9, and many other applications and drivers. Connection pooling is also provided to increase performance with applications such as PHP.
2001-11-05Note conflict with forthcoming unixodbc package.jlam1-1/+3
2001-11-04The PyGreSQL module here has some nasty bugs which will be fixed in thedarcy2-1/+260
next distribution. This patch brings it up to date now. Major fixes: - Support for more types. This fixes a bug introduced in the current PostgreSQL because of the different way of handling agregates. - Add WIN32 support - Fix some DB-API quoting problems
2001-11-02Strongly buildlinkify. Note dependency on tcp_wrappers for platformsjlam4-33/+13
without -lwrap. Also prevent finding any existing Berkeley DB 3.x in /usr/local.
2001-11-02Strongly buildlinkify. Note missing dependency on zlib for platforms thatjlam5-40/+65
don't have a system zlib. Add a buildlink.mk file for use by other package Makefiles.
2001-11-01Move pkg/ files into package's toplevel directoryzuntum10-8/+8
2001-11-01Oops, restore proper distinfozuntum1-3/+3
2001-11-01Oops, back out previous. This locally modified file wasn't supposedzuntum1-2/+2
to be checked in.
2001-11-01Move pkg/ files into package's toplevel directoryzuntum174-94/+94
2001-10-27The ndbm code was preprocessed out of the sources because the symbol definedjlam3-1/+25
in config.h wasn't being used. Fix this by including config.h in the relevant dba_*.c files.
2001-10-27Turn this into an explicit openldap1 dependency, for now.kleink1-2/+2
2001-10-27Use buildlink for gtk and openldap dependencies.kleink1-5/+4
2001-10-26Be explicit about an OpenSSL dependency.kleink1-1/+3
2001-10-26Update for 2.0.18 as well.kleink1-4/+4
2001-10-26Update to OpenLDAP 2.0.18; notable changes:kleink2-5/+5
OpenLDAP 2.0.18 Release Fixed -llber ber_bvecadd bug (ITS#1398) Fixed slap tools replica config bug (ITS#1385) Build environment Updated req_query detection
2001-10-25Update for OpenLDAP-2.0.x.kleink1-2/+5
2001-10-25I'll assume maintainance of this.kleink1-2/+2
2001-10-25Descend into openldap1.kleink1-1/+2
2001-10-25As discussed with Matthias, re-import the previous OpenLDAP packagekleink9-0/+368
as openldap1 for those who want to follow the 1.2.x release branch.
2001-10-25Update "openldap" package to version 2.0.17. Major changes since versiontron5-63/+168
1.2.13: - LDAPv3 support + RFC 2251-2256 + Language Tags (RFC 2596) + SASL (RFC2829) + TLS (RFC2830) and SSL (ldaps://) + named references + DNS SRV location - IPv6 support - LDAP over IPC support - Updated C API - LDIFv1 (RFC2849) - Enhanced Standalone LDAP Server: + Updated Access Control System + Thread Pooling + DNS SRV referral backend (experimental) + LDAP backend (experimental) + SQL backend (experimental) + Better tools This fixes PR pkg/14339 by Hauke Fath.
2001-10-24I am a triple idiot. The only relevant variable that x11.buildlink.mkjlam2-4/+4
redefines about which buildlink.mk files would care is BUILDLINK_X11_DIR, which points to the location of the X11R6 hierarchy used during building. If x11.buildlink.mk isn't included, then BUILDLINK_X11_DIR defaults to ${X11BASE} (set in bsd.pkg.mk), so its value is always safe to use. Remove the ifdefs surrounding the use of BUILDLINK_X11_DIR in tk/buildlink.mk and revert changes to move x11.buildlink.mk before the other buildlink.mk files.
2001-10-23x11.buildlink.mk needs to be included before any buildlink.mk files thatjlam1-2/+2
use X11_BUILDLINK_MK as a test value. Generally just reordering the inclusions so that x11.buildlink.mk comes before the other buildlink.mk files will make everthing work.
2001-10-23Strongly buildlinkify.jlam1-2/+2
2001-10-23- Use buildlink.mk instead of DEPENDSmartti4-275/+9
- Use distfile and patches/* from ../db3 - Updated version to 3.2.9.2 - Apply two patches from the master distribution site 3.2.9.1 Fix a bug where running recovery on a database environment containing only logs from a previous release of Berkeley DB, in which log.0000000001 doesn't exist, could fail. 3.2.9.2 Fix a bug where opening too many files causes a core dump.
2001-10-23* Apply two patches from the master distribution site;lukem4-13/+59
3.2.9.1 Fix a bug where running recovery on a database environment containing only logs from a previous release of Berkeley DB, in which log.0000000001 doesn't exist, could fail. 3.2.9.2 Fix a bug where opening too many files causes a core dump. * Use ${BSD_INSTALL_*} instead of cp, so that bin/db3_* and include/db3/* get installed with the correct ownership * Crank version from 2.9 to 2.9.2
2001-10-20Hmm... shouldn't have forgotten to ad the patches themselves.... (AHUM)reinoud6-0/+222
2001-10-20Patch to make sqlite work on LP64 machines. I tried to make the patch asreinoud2-4/+10
less invasive as posible without rewriting stuff. The main problems were the assumption that a pointer and an int had the same size. Also there were strange casts near calculations that were not nessisary.
2001-10-18SVR4 packages have a limit of 9 chars for a package name.veego16-16/+32
The automatic truncation in gensolpkg doesn't work for packages which have the same package name for the first 5-6 chars. e.g. amanda-server and amanda-client would be named amanda and amanda. Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for amanda-server. All svr4 packages also have a vendor tag, so we have to reserve some chars for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6 or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the vendor tag enough room. All p5-* packages and a few other packages have now a SVR4_PKGNAME.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-09 09:57:30 +0000