Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
Changes from previous:
----------------------
0.09 2011-04-29
- Fix documentation to point at the tutorial, rather than
old advent article.
- Link to Catalyst::ActionRole::ACL
- Tidy up examples to show the new authentication system
- fix check_* to always return scalar values,
even in list context (RT#66812)
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!
pkgsrc changes:
- add license definition (perl license)
- move dependecy to Test::Exception to BUILD_DEPENDS (required for
testing only)
Upstream changes:
0.08 2009-11-19
- repackaged with a new version of Module::Install
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.
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=...").
Role based access control is very simple: every user has a list of
roles, which that user is allowed to assume, and every restricted part
of the app makes an assertion about the necessary roles.
If the user is a member in all of the required roles access is granted.
Otherwise, access is denied.
WWW: http://search.cpan.org/dist/Catalyst-Plugin-Authorization-Roles/
