Clearly state which version of SQLite is supported.

5 files changed, 29 insertions, 29 deletions

diff --git a/databases/ruby-sqlite/Makefile b/databases/ruby-sqlite/Makefile
index 17fa00a..457fd04 100644
--- a/databases/ruby-sqlite/Makefile
+++ b/databases/ruby-sqlite/Makefile
@@ -14,7 +14,7 @@ DISTNAME=	${PORTNAME}-ruby-${PORTVERSION}
 DIST_SUBDIR=	ruby
 
 MAINTAINER=	knu@FreeBSD.org
-COMMENT=	Ruby interface to the SQLite DB engine
+COMMENT=	Ruby interface to the SQLite DB engine version 2
 
 LIB_DEPENDS=	sqlite.2:${PORTSDIR}/databases/sqlite2
 
diff --git a/databases/ruby-sqlite/pkg-descr b/databases/ruby-sqlite/pkg-descr
index da58457..5811e05 100644
--- a/databases/ruby-sqlite/pkg-descr
+++ b/databases/ruby-sqlite/pkg-descr
@@ -1,9 +1,9 @@
-sqlite-ruby provides an interface for the SQLite DB engine.  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.
+sqlite-ruby provides an interface for the SQLite DB engine version 2.
+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:	minam <jgb3@email.byu.edu>
+Author:	Jamis Buck (minam) <jgb3@email.byu.edu>
 WWW:	http://sqlite-ruby.rubyforge.org
diff --git a/databases/ruby-sqlite3/pkg-descr b/databases/ruby-sqlite3/pkg-descr
index da58457..7cca1fe 100644
--- a/databases/ruby-sqlite3/pkg-descr
+++ b/databases/ruby-sqlite3/pkg-descr
@@ -1,9 +1,9 @@
-sqlite-ruby provides an interface for the SQLite DB engine.  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.
+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:	minam <jgb3@email.byu.edu>
+Author:	Jamis Buck (minam) <jgb3@email.byu.edu>
 WWW:	http://sqlite-ruby.rubyforge.org
diff --git a/databases/rubygem-sqlite3-ruby/pkg-descr b/databases/rubygem-sqlite3-ruby/pkg-descr
index da58457..7cca1fe 100644
--- a/databases/rubygem-sqlite3-ruby/pkg-descr
+++ b/databases/rubygem-sqlite3-ruby/pkg-descr
@@ -1,9 +1,9 @@
-sqlite-ruby provides an interface for the SQLite DB engine.  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.
+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:	minam <jgb3@email.byu.edu>
+Author:	Jamis Buck (minam) <jgb3@email.byu.edu>
 WWW:	http://sqlite-ruby.rubyforge.org
diff --git a/databases/rubygem-sqlite3/pkg-descr b/databases/rubygem-sqlite3/pkg-descr
index da58457..7cca1fe 100644
--- a/databases/rubygem-sqlite3/pkg-descr
+++ b/databases/rubygem-sqlite3/pkg-descr
@@ -1,9 +1,9 @@
-sqlite-ruby provides an interface for the SQLite DB engine.  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.
+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:	minam <jgb3@email.byu.edu>
+Author:	Jamis Buck (minam) <jgb3@email.byu.edu>
 WWW:	http://sqlite-ruby.rubyforge.org