kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/www/p5-Catalyst-Action-REST/Makefile

34 lines
1.2 KiB
Makefile
Raw Normal View History

Bump the PKGREVISION for all packages which depend directly on perl, to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1. The list of packages is computed by finding all packages which end up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl, or PERL5_PACKLIST defined in their make setup (tested via "make show-vars VARNAMES=..."), minus the packages updated after the perl package update. sno@ was right after all, obache@ kindly asked and he@ led the way. Thanks!
2010-08-21 18:32:42 +02:00
# $NetBSD: Makefile,v 1.8 2010/08/21 16:36:38 seb Exp $
Added www/p5-Catalyst-Action-REST version 0.76 This Action handles doing automatic method dispatching for REST requests. It takes a normal Catalyst action, and changes the dispatch to append an underscore and method name. For example, in the synopsis above, calling GET on "/foo" would result in the foo_GET method being dispatched. If a method is requested that is not implemented, this action will return a status 405 (Method Not Found). It will populate the "Allow" header with the list of implemented request methods. You can override this behavior by implementing a custom 405 handler like so: sub foo_not_implemented { ... handle not implemented methods ... } If you do not provide an _OPTIONS subroutine, we will automatically respond with a 200 OK. The "Allow" header will be populated with the list of implemented request methods. It is likely that you really want to look at Catalyst::Controller::REST, which brings this class together with automatic Serialization of requests and responses.
2009-08-27 12:37:24 +02:00
Updating www/p5-Catalyst-Action-REST from 0.81 to 0.83 Upstream changes: Mon 8 Feb 2010 22:17:12 GMT - Release 0.83 Make it possible to deserialize a request with a DELETE method. This probably breaks 'strict' REST guidelines, but is useful for being able to delete multiple resources from a single call by providing a batch delete method. Remove JSONP from the list of default serializers (RT#54336) Fix MANIFEST (RT#54408) Thu 4 Feb 2010 22:31:57 GMT - Release 0.82 Integrated Catalyst::Request::REST::ForBrowsers as Catalyst::TraitFor::Request::ForBrowsers. (Dave Rolsky) Clarified docs so that they encourage the use of the request traits, rather than using Catalyst::Request::REST. (Dave Rolsky) When Catalyst::Action::REST or Controller::REST automatically add the trait, your request class will no longer end up getting set to Catalyst::Request::REST. Instead, creates an anon class with the appropriate role. (Dave Rolsky) Shut up log output from the tests. (Dave Rolsky) Added a $VERSION to every module, mostly to make sure that when people install Catalyst::Request::REST::ForBrowsers, they get the version in this distro. (Dave Rolsky) Change Catalyst::Action::Serialize, Catalyst::Action::Deserialize and Catalyst::Action::SerializeBase to be more Moose like. Fix JSON and JSON::XS to encode_blessed. (fREW) Fix Catalyst::Action::Serialize to use objects instead of classes. (fREW) Fix doc nits. (RT#53780)
2010-03-10 12:02:23 +01:00
DISTNAME= Catalyst-Action-REST-0.83
Added www/p5-Catalyst-Action-REST version 0.76 This Action handles doing automatic method dispatching for REST requests. It takes a normal Catalyst action, and changes the dispatch to append an underscore and method name. For example, in the synopsis above, calling GET on "/foo" would result in the foo_GET method being dispatched. If a method is requested that is not implemented, this action will return a status 405 (Method Not Found). It will populate the "Allow" header with the list of implemented request methods. You can override this behavior by implementing a custom 405 handler like so: sub foo_not_implemented { ... handle not implemented methods ... } If you do not provide an _OPTIONS subroutine, we will automatically respond with a 200 OK. The "Allow" header will be populated with the list of implemented request methods. It is likely that you really want to look at Catalyst::Controller::REST, which brings this class together with automatic Serialization of requests and responses.
2009-08-27 12:37:24 +02:00
PKGNAME= p5-${DISTNAME}
Bump the PKGREVISION for all packages which depend directly on perl, to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1. The list of packages is computed by finding all packages which end up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl, or PERL5_PACKLIST defined in their make setup (tested via "make show-vars VARNAMES=..."), minus the packages updated after the perl package update. sno@ was right after all, obache@ kindly asked and he@ led the way. Thanks!
2010-08-21 18:32:42 +02:00
PKGREVISION= 1
Added www/p5-Catalyst-Action-REST version 0.76 This Action handles doing automatic method dispatching for REST requests. It takes a normal Catalyst action, and changes the dispatch to append an underscore and method name. For example, in the synopsis above, calling GET on "/foo" would result in the foo_GET method being dispatched. If a method is requested that is not implemented, this action will return a status 405 (Method Not Found). It will populate the "Allow" header with the list of implemented request methods. You can override this behavior by implementing a custom 405 handler like so: sub foo_not_implemented { ... handle not implemented methods ... } If you do not provide an _OPTIONS subroutine, we will automatically respond with a 200 OK. The "Allow" header will be populated with the list of implemented request methods. It is likely that you really want to look at Catalyst::Controller::REST, which brings this class together with automatic Serialization of requests and responses.
2009-08-27 12:37:24 +02:00
CATEGORIES= www perl5
MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=Catalyst/}
MAINTAINER= pkgsrc-users@NetBSD.org
HOMEPAGE= http://search.cpan.org/dist/Catalyst-Action-REST/
COMMENT= Automated REST Method Dispatching
LICENSE= ${PERL5_LICENSE}
Updating www/p5-Catalyst-Action-REST from 0.78 to 0.81 pkgsrc changes: - Adjusting dependencies - Adjust module type Upstream changes: Thu 14 Jan 20:56:00 GMT 2010 - Release 0.81 Add a JSONP serialization type. Sat 19 Dec 14:54:00 GMT 2009 - Release 0.80 Convert all classes to Moose Change Catalyst::Request::REST to be a mostly empty class, with all the functionality in Catalyst::TraitFor::Request::REST Simplify _get_allowed_methods method (aristotle) Rework serializer return so that serializers throw an exception in the case of issues serializing the data (hobbs). Fri 11 Dec 01:08:00 GMT 2009 - Release 0.79 Cope with invalid (missing required q parameter) header like: application/json; charset="utf-8" Fix documentation to not mention deprecated things and generally be in better style. Make author information consistant and only in one module.
2010-02-02 12:43:13 +01:00
DEPENDS+= p5-Catalyst-Runtime>=5.80000:../../www/p5-Catalyst-Runtime
DEPENDS+= p5-Class-Inspector>=1.13:../../devel/p5-Class-Inspector
DEPENDS+= p5-Data-Serializer>=0.36:../../devel/p5-Data-Serializer
DEPENDS+= p5-MRO-Compat>=0.10:../../devel/p5-MRO-Compat
DEPENDS+= {perl>=5.10,p5-Module-Pluggable-[0-9]*}:../../devel/p5-Module-Pluggable
DEPENDS+= p5-Moose-[0-9]*:../../devel/p5-Moose
DEPENDS+= p5-Params-Validate>=0.76:../../devel/p5-Params-Validate
DEPENDS+= p5-URI-Find>=0:../../www/p5-URI-Find
DEPENDS+= p5-YAML-Syck>=0.67:../../textproc/p5-YAML-Syck
DEPENDS+= p5-libwww>=5.831:../../www/p5-libwww
DEPENDS+= p5-namespace-autoclean-[0-9]*:../../devel/p5-namespace-autoclean
Added www/p5-Catalyst-Action-REST version 0.76 This Action handles doing automatic method dispatching for REST requests. It takes a normal Catalyst action, and changes the dispatch to append an underscore and method name. For example, in the synopsis above, calling GET on "/foo" would result in the foo_GET method being dispatched. If a method is requested that is not implemented, this action will return a status 405 (Method Not Found). It will populate the "Allow" header with the list of implemented request methods. You can override this behavior by implementing a custom 405 handler like so: sub foo_not_implemented { ... handle not implemented methods ... } If you do not provide an _OPTIONS subroutine, we will automatically respond with a 200 OK. The "Allow" header will be populated with the list of implemented request methods. It is likely that you really want to look at Catalyst::Controller::REST, which brings this class together with automatic Serialization of requests and responses.
2009-08-27 12:37:24 +02:00
Updating www/p5-Catalyst-Action-REST from 0.78 to 0.81 pkgsrc changes: - Adjusting dependencies - Adjust module type Upstream changes: Thu 14 Jan 20:56:00 GMT 2010 - Release 0.81 Add a JSONP serialization type. Sat 19 Dec 14:54:00 GMT 2009 - Release 0.80 Convert all classes to Moose Change Catalyst::Request::REST to be a mostly empty class, with all the functionality in Catalyst::TraitFor::Request::REST Simplify _get_allowed_methods method (aristotle) Rework serializer return so that serializers throw an exception in the case of issues serializing the data (hobbs). Fri 11 Dec 01:08:00 GMT 2009 - Release 0.79 Cope with invalid (missing required q parameter) header like: application/json; charset="utf-8" Fix documentation to not mention deprecated things and generally be in better style. Make author information consistant and only in one module.
2010-02-02 12:43:13 +01:00
USE_LANGUAGES= # empty
PERL5_PACKLIST= auto/Catalyst/Action/REST/.packlist
PERL5_MODULE_TYPE= Module::Install::Bundled
Added www/p5-Catalyst-Action-REST version 0.76 This Action handles doing automatic method dispatching for REST requests. It takes a normal Catalyst action, and changes the dispatch to append an underscore and method name. For example, in the synopsis above, calling GET on "/foo" would result in the foo_GET method being dispatched. If a method is requested that is not implemented, this action will return a status 405 (Method Not Found). It will populate the "Allow" header with the list of implemented request methods. You can override this behavior by implementing a custom 405 handler like so: sub foo_not_implemented { ... handle not implemented methods ... } If you do not provide an _OPTIONS subroutine, we will automatically respond with a 200 OK. The "Allow" header will be populated with the list of implemented request methods. It is likely that you really want to look at Catalyst::Controller::REST, which brings this class together with automatic Serialization of requests and responses.
2009-08-27 12:37:24 +02:00
PKG_DESTDIR_SUPPORT= user-destdir
.include "../../lang/perl5/module.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink