kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/www/p5-Rose-URI/Makefile

22 lines
601 B
Makefile
Raw Normal View History

Update from version 0.022nb1 to 0.500 (upstream 0.50): Pkgsrc changes: o Canonicalize HOMEPAGE Upstream changes: 0.50 (10.21.2008) - John Siracusa <siracusa@gmail.com> * Fixed a bug that caused empty query parameters to be omitted from the query string. * Added the omit_empty_query_params object attribute (with class- wide default override) to preserve the old behavior.
2008-12-16 22:44:06 +01:00
# $NetBSD: Makefile,v 1.3 2008/12/16 21:44:06 he Exp $
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.
2008-07-15 10:44:22 +02:00
Update from version 0.022nb1 to 0.500 (upstream 0.50): Pkgsrc changes: o Canonicalize HOMEPAGE Upstream changes: 0.50 (10.21.2008) - John Siracusa <siracusa@gmail.com> * Fixed a bug that caused empty query parameters to be omitted from the query string. * Added the omit_empty_query_params object attribute (with class- wide default override) to preserve the old behavior.
2008-12-16 22:44:06 +01:00
DISTNAME= Rose-URI-0.50
PKGNAME= p5-${DISTNAME}0
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.
2008-07-15 10:44:22 +02:00
CATEGORIES= devel perl5
MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=Rose/}
MAINTAINER= pkgsrc-users@NetBSD.org
Update from version 0.022nb1 to 0.500 (upstream 0.50): Pkgsrc changes: o Canonicalize HOMEPAGE Upstream changes: 0.50 (10.21.2008) - John Siracusa <siracusa@gmail.com> * Fixed a bug that caused empty query parameters to be omitted from the query string. * Added the omit_empty_query_params object attribute (with class- wide default override) to preserve the old behavior.
2008-12-16 22:44:06 +01:00
HOMEPAGE= http://search.cpan.org/dist/Rose-URI/
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.
2008-07-15 10:44:22 +02:00
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"
Reference in a new issue Copy permalink