1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
|
Source: libcriticism-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: Onur Aslan <onur@onur.im>
Section: perl
Priority: optional
Build-Depends: debhelper (>= 8), libmodule-build-perl
Build-Depends-Indep: libio-string-perl, libperl-critic-perl, perl
Standards-Version: 3.9.6
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-perl/packages/libcriticism-perl.git
Vcs-Git: git://anonscm.debian.org/pkg-perl/packages/libcriticism-perl.git
Homepage: https://metacpan.org/release/criticism
Testsuite: autopkgtest-pkg-perl
Package: libcriticism-perl
Architecture: all
Depends: ${misc:Depends}, ${perl:Depends}
Recommends: libperl-critic-perl
Description: Perl pragma to enforce coding standards and best-practices
The cristicism pragma enforces coding standards and promotes best-practices
by running your file through Perl::Critic before every execution. In a
production system, this usually isn't feasible because it adds a lot of
overhead at start-up. If you have a separate development environment,
you can effectively bypass the "criticism" pragma by not installing
Perl::Critic in the production environment. If Perl::Critic can't be
loaded, then "criticism" just fails silently.
|
