Added www/p5-Rose-URI version 0.022

Rose::URI is an alternative to URI. Important differences include:

Rose::URI provides a rich set of query string manipulation methods.
Query parameters can be added, removed, and checked for their
existence. URI allows the entire query to be set or returned as a
whole via the query_form or query methods, and the URI::QueryParam
module provides a few more methods for query string manipulation.

Rose::URI supports query parameters with multiple values (e.g.
"a=1&a=2"). URI has limited support for this through query_form's
list return value. Better methods are available in URI::QueryParam.

Rose::URI uses Apache's C-based URI parsing and HTML escaping
functions when running in a mod_perl 1.x web server environment.

Rose::URI stores each URI "in pieces" (scheme, host, path, etc.)
and then assembles those pieces when the entire URI is needed as
a string. This technique is based on the assumption that the URI
will be manipulated many more times than it is stringified. If this
is not the case in your usage scenario, then URI may be a better
alternative.

3 files changed, 47 insertions, 0 deletions

diff --git a/www/p5-Rose-URI/DESCR b/www/p5-Rose-URI/DESCR
new file mode 100644
index 00000000000..e714cd5e14a
--- /dev/null
+++ b/www/p5-Rose-URI/DESCR
@@ -0,0 +1,21 @@
+Rose::URI is an alternative to URI. Important differences include:
+
+Rose::URI provides a rich set of query string manipulation methods.
+Query parameters can be added, removed, and checked for their
+existence. URI allows the entire query to be set or returned as a
+whole via the query_form or query methods, and the URI::QueryParam
+module provides a few more methods for query string manipulation.
+
+Rose::URI supports query parameters with multiple values (e.g.
+"a=1&a=2"). URI has limited support for this through query_form's
+list return value. Better methods are available in URI::QueryParam.
+
+Rose::URI uses Apache's C-based URI parsing and HTML escaping
+functions when running in a mod_perl 1.x web server environment.
+
+Rose::URI stores each URI "in pieces" (scheme, host, path, etc.)
+and then assembles those pieces when the entire URI is needed as
+a string. This technique is based on the assumption that the URI
+will be manipulated many more times than it is stringified. If this
+is not the case in your usage scenario, then URI may be a better
+alternative.
diff --git a/www/p5-Rose-URI/Makefile b/www/p5-Rose-URI/Makefile
new file mode 100644
index 00000000000..ca91dab640b
--- /dev/null
+++ b/www/p5-Rose-URI/Makefile
@@ -0,0 +1,21 @@
+# $NetBSD: Makefile,v 1.1.1.1 2008/07/15 08:44:22 abs Exp $
+
+DISTNAME=	Rose-URI-0.022
+PKGNAME=	p5-${DISTNAME}
+CATEGORIES=	devel perl5
+MASTER_SITES=	${MASTER_SITE_PERL_CPAN:=Rose/}
+
+MAINTAINER=	pkgsrc-users@NetBSD.org
+HOMEPAGE=	http://search.cpan.org/perldoc?Rose::URI
+COMMENT=	URI class for easy and efficient manipulation of URI components
+
+DEPENDS+=	p5-Rose-Object>=0.15:../../devel/p5-Rose-Object
+DEPENDS+=	p5-URI>=0:../../www/p5-URI
+
+USE_LANGUAGES=	# empty
+PERL5_PACKLIST=	auto/Rose/URI/.packlist
+
+PKG_DESTDIR_SUPPORT=    user-destdir
+
+.include "../../lang/perl5/module.mk"
+.include "../../mk/bsd.pkg.mk"
diff --git a/www/p5-Rose-URI/distinfo b/www/p5-Rose-URI/distinfo
new file mode 100644
index 00000000000..f556b095683
--- /dev/null
+++ b/www/p5-Rose-URI/distinfo
@@ -0,0 +1,5 @@
+$NetBSD: distinfo,v 1.1.1.1 2008/07/15 08:44:22 abs Exp $
+
+SHA1 (Rose-URI-0.022.tar.gz) = 77b0d056b4fe888543f5606310aa82414239989f
+RMD160 (Rose-URI-0.022.tar.gz) = 027c284b625814a1f46713accf7db098553eaa83
+Size (Rose-URI-0.022.tar.gz) = 8260 bytes