summaryrefslogtreecommitdiff
path: root/databases/rubygem-sqlite3-ruby
diff options
context:
space:
mode:
Diffstat (limited to 'databases/rubygem-sqlite3-ruby')
-rw-r--r--databases/rubygem-sqlite3-ruby/Makefile26
-rw-r--r--databases/rubygem-sqlite3-ruby/distinfo3
-rw-r--r--databases/rubygem-sqlite3-ruby/pkg-descr9
3 files changed, 0 insertions, 38 deletions
diff --git a/databases/rubygem-sqlite3-ruby/Makefile b/databases/rubygem-sqlite3-ruby/Makefile
deleted file mode 100644
index c6492884ab8c..000000000000
--- a/databases/rubygem-sqlite3-ruby/Makefile
+++ /dev/null
@@ -1,26 +0,0 @@
-# New ports collection makefile for: sqlite3-ruby
-# Date created: 26 June 2003
-# Whom: Akinori MUSHA aka knu <knu@idaemons.org>
-#
-# $FreeBSD$
-#
-
-PORTNAME= sqlite3
-PORTVERSION= 1.2.5
-CATEGORIES= databases rubygems
-MASTER_SITES= RUBYFORGE/sqlite-ruby
-DISTNAME= ${PORTNAME}-ruby-${PORTVERSION}
-
-MAINTAINER= ruby@FreeBSD.org
-COMMENT= Ruby interface to the SQLite DB engine version 3
-
-BUILD_DEPENDS= swig:${PORTSDIR}/devel/swig13
-LIB_DEPENDS= sqlite3.8:${PORTSDIR}/databases/sqlite3
-
-USE_RUBY= yes
-USE_RUBYGEMS= yes
-CONFIGURE_ARGS+=--with-sqlite3-dir=${LOCALBASE}
-GEM_NAME= ${DISTNAME}
-RUBYGEM_AUTOPLIST= yes
-
-.include <bsd.port.mk>
diff --git a/databases/rubygem-sqlite3-ruby/distinfo b/databases/rubygem-sqlite3-ruby/distinfo
deleted file mode 100644
index eb7245f8a356..000000000000
--- a/databases/rubygem-sqlite3-ruby/distinfo
+++ /dev/null
@@ -1,3 +0,0 @@
-MD5 (rubygem/sqlite3-ruby-1.2.5.gem) = eaa6328b0e971f4563f8d26715e37e13
-SHA256 (rubygem/sqlite3-ruby-1.2.5.gem) = b94611a60e1f336b68291010f66e112e5c18c0808d3f45c16d779d3619e51d3b
-SIZE (rubygem/sqlite3-ruby-1.2.5.gem) = 74240
diff --git a/databases/rubygem-sqlite3-ruby/pkg-descr b/databases/rubygem-sqlite3-ruby/pkg-descr
deleted file mode 100644
index 7cca1fe5102f..000000000000
--- a/databases/rubygem-sqlite3-ruby/pkg-descr
+++ /dev/null
@@ -1,9 +0,0 @@
-sqlite3-ruby provides an interface for the SQLite DB engine version 3.
-This differs from the DBD::SQLite module in that it is more complete,
-and from the ruby DBI version of SQLite in that it is SQLite specific,
-so you can do things that would otherwise be more difficult via DBI.
-If you want portability between backends, use DBI. If you want ease
-of use with SQLite, use this.
-
-Author: Jamis Buck (minam) <jgb3@email.byu.edu>
-WWW: http://sqlite-ruby.rubyforge.org