summaryrefslogtreecommitdiff
path: root/databases/unixodbc
AgeCommit message (Collapse)AuthorFilesLines
2006-04-12Aligned the last line of the buildlink3.mk files with the first line, sorillig1-2/+2
that they look nicer.
2006-04-06Over 1200 files touched but no revisions bumped :)reed1-3/+3
RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-01-23Commit modified patch missed in previous.xtraeme1-8/+8
2006-01-23Update unixodbc-* packages to 2.2.11 (latest stable version).xtraeme4-20/+20
See http://www.unixodbc.org/ for the list of changes... sorry but this package was not updated in 5 years, the list might be very large!
2006-01-06Use SUBST framework.joerg1-4/+9
2005-12-29Remove USE_PKGINSTALL from pkgsrc now that mk/install/pkginstall.mkjlam1-2/+1
automatically detects whether we want the pkginstall machinery to be used by the package Makefile.
2005-12-05Ran "pkglint --autofix", which corrected some of the quoting issues inrillig1-3/+3
CONFIGURE_ARGS.
2005-12-05Fixed pkglint warnings. The warnings are mostly quoting issues, forrillig1-3/+3
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some other changes are outlined in http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
2005-11-09USE_TOOLS+=flex; without this, libodbctxt.la (without the 'S') is not built.tv1-2/+3
Bump PKGREVISION.
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-23Add RMD160 digests in addition to SHA1 ones.agc1-1/+2
2005-01-19Properly quote the MAKE_FLAGS.reed1-2/+2
This is from PR #29009 from Masanori Mikawa. When built when using cpuflags includes, the quoting for AM_MAKEFLAGS is wrong.
2004-10-15Update linkage to libltdl, now in its own package.tv3-8/+5
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-30PKGREVISION doesn't belong here; the individual Makefiles set it.tv1-2/+1
2004-09-22Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.jlam1-91/+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-04-26Unused.wiz1-34/+0
2004-04-25bl3ifyxtraeme3-6/+27
2004-04-24Relinquish maintainership of packages to tech-pkg@NetBSD.org.jlam1-2/+2
2004-02-14LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now lists of shell globsjlam1-2/+1
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that are automatically handled by the default setting in bsd.pkg.mk.
2004-01-27Use $FIND with "-print". Noted by Georg Schwarz in PR pkg/24248heinz1-3/+3
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-05-02Dependency bumps, needed because of devel/pth's major bump, and relatedwiz3-5/+6
dependency bumps.
2003-01-28Instead of including bsd.pkg.install.mk directly in a package Makefile,jlam1-2/+2
have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set to "YES". This enforces the requirement that bsd.pkg.install.mk be included at the end of a package Makefile. Idea suggested by Julio M. Merino Vidal <jmmv at menta.net>.
2003-01-19Use "mk/pthread.buildlink2.mk" instead of "devel/pth/buildlink2.mk" totron1-2/+2
use native threads on platforms which support them.
2002-09-20All users of unixodbc/buildlink.mk have been converted to use buildlink2.jlam1-51/+0
2002-09-20buildlink1 -> buildlink2jlam2-8/+8
2002-08-25Merge changes in packages from the buildlink2 branch that havejlam4-3/+37
buildlink2.mk files back into the main trunk.
2002-08-08These packages install libraries that differ from previous versions if theyjlam1-1/+2
are built using the hard-syscall-enabled pth. Bump the PKGREVISION so we can distinguish these packages from the previous ones.
2002-08-01Convert to use pthread.buildlink.mk.jlam2-6/+12
2001-12-04Remove unused variables now that we use PKGREVISION.jlam1-5/+1
2001-12-03Use PKGREVISION to manage the package-specific version number when itjlam1-3/+2
differs from the distfile version number. G/C some the unused variables in unixodbc/Makefile.common related to the old way of handling version numbers.
2001-12-02bsd.pkg.install.mk calls the INSTALL script at the right timesjlam1-3/+1
automatically, so no need to do it ourselves.
2001-11-26Forgot a CONFDIR -> PKG_SYSCONFDIR replacement.jlam1-2/+2
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-19Adapt to use shared INSTALL/DEINSTALL scripts by using the logic injlam4-188/+10
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-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-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.