This is an automated email from the git hooks/post-receive script.

dmn pushed a commit to branch master
in repository libcatalyst-plugin-authorization-roles-perl.

commit f6f5d773e6099303dcd5ae39c8f461c031e467c8
Author: Damyan Ivanov <>
Date:   Wed May 14 14:32:48 2014 +0000

    update description
 debian/control | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/debian/control b/debian/control
index e1a9ec4..583ceae 100644
--- a/debian/control
+++ b/debian/control
@@ -24,20 +24,20 @@ Depends: ${misc:Depends}, ${perl:Depends},
  libuniversal-isa-perl (>= 0.05)
 Replaces: libcatalyst-modules-perl (<< 47~)
 Breaks: libcatalyst-modules-perl (<< 47~)
-Description: Role based authorization for Catalyst based on 
+Description: Role based authorization plugin for Catalyst
+ Catalyst::Plugin::Authorization::Roles provides role-based authorization
+ (access control) for Catalyst applications.
+ .
  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.
  With assert_user_roles, if the user is a member in all of the required roles
  access is granted. Otherwise, access is denied. With assert_any_user_role it
- is enough that the user is a member in one role.
+ is enough that the user is a member of one role.
  There are alternative approaches to do this on a per action basis, see
- For example, if you have a CRUD application, for every mutating action you
- probably want to check that the user is allowed to edit. To do this, create
- an editor role, and add that role to every user who is allowed to edit.
- .
- This description was automagically extracted from the module by dh-make-perl.
+ Catalyst is an elegant Model-View-Controller web application framework
+ written in Perl.

Alioth's /usr/local/bin/git-commit-notice on 

Pkg-perl-cvs-commits mailing list

Reply via email to