Initial import of datadraw-3.1.1

DataDraw is an ultra-fast persistent database for high performance programs
written in C.  It's so fast that many programs keep all their data in a
DataDraw database, even while being manipulated in inner loops of compute
intensive applications.  DataDraw databases are compiled, and directly link
into your C programs.  DataDraw databases are resident in memory, making data
manipulation even faster than if they were stored in native C data structures
(really).

DataDraw databases can be persistent.  Modifications to persistent data are
written to disk as they are made, which of course dramatically slows write
times.  However, DataDraw databases can also be volatile.  Volatile databases
exist only in memory, and only for the duration that your program needs it.
Volatile databases can be directly manipulated faster than C structures, since
data is better organized in memory to optimize cache performance

DataDraw supports modular design.  An application can have one or more common
persistent databases, and multiple volatile databases to support various tools'
data structures.  Classes in a tool's database can extend classes in the common
database.

DataDraw is also 64-bit optimized, allowing programs to run much faster and in
less memory than standard C programs using 64-bit pointers.  This is because
DataDraw databases supports over 4 billion objects of a given class with 32-bit
object references.

5 files changed, 88 insertions, 0 deletions

diff --git a/databases/datadraw/DESCR b/databases/datadraw/DESCR
new file mode 100644
index 00000000000..9dd6eafc3a1
--- /dev/null
+++ b/databases/datadraw/DESCR
@@ -0,0 +1,24 @@
+DataDraw is an ultra-fast persistent database for high performance programs
+written in C.  It's so fast that many programs keep all their data in a
+DataDraw database, even while being manipulated in inner loops of compute
+intensive applications.  DataDraw databases are compiled, and directly link
+into your C programs.  DataDraw databases are resident in memory, making data
+manipulation even faster than if they were stored in native C data structures
+(really).
+
+DataDraw databases can be persistent.  Modifications to persistent data are
+written to disk as they are made, which of course dramatically slows write
+times.  However, DataDraw databases can also be volatile.  Volatile databases
+exist only in memory, and only for the duration that your program needs it.
+Volatile databases can be directly manipulated faster than C structures, since
+data is better organized in memory to optimize cache performance
+
+DataDraw supports modular design.  An application can have one or more common
+persistent databases, and multiple volatile databases to support various tools'
+data structures.  Classes in a tool's database can extend classes in the common
+database.
+
+DataDraw is also 64-bit optimized, allowing programs to run much faster and in
+less memory than standard C programs using 64-bit pointers.  This is because
+DataDraw databases supports over 4 billion objects of a given class with 32-bit
+object references.
diff --git a/databases/datadraw/Makefile b/databases/datadraw/Makefile
new file mode 100644
index 00000000000..e138680370d
--- /dev/null
+++ b/databases/datadraw/Makefile
@@ -0,0 +1,27 @@
+# $NetBSD: Makefile,v 1.1.1.1 2009/11/25 22:42:35 dmcmahill Exp $
+#
+
+DISTNAME=	datadraw3.1.1
+PKGNAME=	datadraw-3.1.1
+CATEGORIES=	databases
+MASTER_SITES=	${MASTER_SITE_SOURCEFORGE:=datadraw/}
+
+MAINTAINER=	pkgsrc-users@NetBSD.org
+HOMEPAGE=	http://datadraw.sourceforge.net/
+COMMENT=	Persistent database generator for high performance C applications
+
+PKG_INSTALLATION_TYPES=	overwrite pkgviews
+PKG_DESTDIR_SUPPORT=	user-destdir
+
+LICENSE=	gnu-lgpl-v2
+
+HAS_CONFIGURE=		yes
+CONFIGURE_ARGS+=	--prefix=${PREFIX}
+CONFIGURE_ARGS+=	CFLAGS=${CFLAGS:Q}
+CONFIGURE_ARGS+=	LDFLAGS=${LDFLAGS:Q}
+USE_TOOLS+=		bash:build bison flex gmake
+CONFIG_SHELL=		${TOOLS_PATH.bash}
+
+BUILD_TARGET=	datadraw
+
+.include "../../mk/bsd.pkg.mk"
diff --git a/databases/datadraw/PLIST b/databases/datadraw/PLIST
new file mode 100644
index 00000000000..2a53850a4ef
--- /dev/null
+++ b/databases/datadraw/PLIST
@@ -0,0 +1,18 @@
+@comment $NetBSD: PLIST,v 1.1.1.1 2009/11/25 22:42:35 dmcmahill Exp $
+bin/datadraw
+include/ddutil.h
+include/utdatabase.h
+include/utdatabasep.h
+include/utdatabaseu.h
+include/utdatabaseup.h
+include/utmem.h
+include/utpersist.h
+include/uttypes.h
+lib/libddutil-dbg.a
+lib/libddutil.a
+lib/libddutilp-dbg.a
+lib/libddutilp.a
+lib/libddutilu-dbg.a
+lib/libddutilu.a
+lib/libddutilup-dbg.a
+lib/libddutilup.a
diff --git a/databases/datadraw/distinfo b/databases/datadraw/distinfo
new file mode 100644
index 00000000000..2bdd05ad83e
--- /dev/null
+++ b/databases/datadraw/distinfo
@@ -0,0 +1,6 @@
+$NetBSD: distinfo,v 1.1.1.1 2009/11/25 22:42:35 dmcmahill Exp $
+
+SHA1 (datadraw3.1.1.tar.gz) = 571c01418556dab427ba95f7c5e7a23a0acb24d1
+RMD160 (datadraw3.1.1.tar.gz) = 03d4ea06ad47d545f1182b1d268a1860e0304d27
+Size (datadraw3.1.1.tar.gz) = 607914 bytes
+SHA1 (patch-aa) = 70e52e7e0724ce3627485d07652e400d73187e8d
diff --git a/databases/datadraw/patches/patch-aa b/databases/datadraw/patches/patch-aa
new file mode 100644
index 00000000000..67ade29c92f
--- /dev/null
+++ b/databases/datadraw/patches/patch-aa
@@ -0,0 +1,13 @@
+$NetBSD: patch-aa,v 1.1.1.1 2009/11/25 22:42:35 dmcmahill Exp $
+
+--- util/configure.orig	2008-03-30 14:42:53.000000000 +0000
++++ util/configure
+@@ -131,7 +131,7 @@ makeMakefileBottom () {
+ " >> Makefile
+     done
+ 
+-    if [ "$SUFFIX" == "$NONDBG_SUFFIX" ]; then
++    if [ "$SUFFIX" = "$NONDBG_SUFFIX" ]; then
+         echo "utdatabase$SUFFIX.c utdatabase$SUFFIX.h: DatadrawUtil.dd
+ 	datadraw $DATADRAW_FLAGS -s utdatabase$SUFFIX.c -h utdatabase$SUFFIX.h DatadrawUtil.dd
+