diff options
Diffstat (limited to 'databases/rubygem-sqlite3-ruby')
| -rw-r--r-- | databases/rubygem-sqlite3-ruby/Makefile | 28 | ||||
| -rw-r--r-- | databases/rubygem-sqlite3-ruby/distinfo | 2 | ||||
| -rw-r--r-- | databases/rubygem-sqlite3-ruby/pkg-descr | 9 |
3 files changed, 0 insertions, 39 deletions
diff --git a/databases/rubygem-sqlite3-ruby/Makefile b/databases/rubygem-sqlite3-ruby/Makefile deleted file mode 100644 index c3f9377a9c92..000000000000 --- a/databases/rubygem-sqlite3-ruby/Makefile +++ /dev/null @@ -1,28 +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.3.2 -CATEGORIES= databases rubygems -MASTER_SITES= RG -DISTNAME= ${PORTNAME}-ruby-${PORTVERSION} - -MAINTAINER= ruby@FreeBSD.org -COMMENT= Ruby interface to the SQLite DB engine version 3 - -LIB_DEPENDS= sqlite3.8:${PORTSDIR}/databases/sqlite3 -BUILD_DEPENDS= swig:${PORTSDIR}/devel/swig13 - -CONFIGURE_ARGS+=--with-sqlite3-dir=${LOCALBASE} - -GEM_NAME= ${DISTNAME} - -USE_RUBY= yes -USE_RUBYGEMS= yes -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 edee85e02063..000000000000 --- a/databases/rubygem-sqlite3-ruby/distinfo +++ /dev/null @@ -1,2 +0,0 @@ -SHA256 (rubygem/sqlite3-ruby-1.3.2.gem) = 9c3d4eb7c3a92bb16bfd2c804bfcd0222539cff0d050e809ec1493959738a64c -SIZE (rubygem/sqlite3-ruby-1.3.2.gem) = 55808 diff --git a/databases/rubygem-sqlite3-ruby/pkg-descr b/databases/rubygem-sqlite3-ruby/pkg-descr deleted file mode 100644 index 869c8a69bfcc..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: https://github.com/qoobaa/sqlite3 |