libcriticism-perl 1.02-3 source package in Ubuntu

Changelog

libcriticism-perl (1.02-3) unstable; urgency=medium

  [ Salvatore Bonaccorso ]
  * debian/control: Use HTTPS transport protocol for Vcs-Git URI

  [ gregor herrmann ]
  * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.

  [ Alex Muntada ]
  * Remove inactive pkg-perl members from Uploaders.

  [ Salvatore Bonaccorso ]
  * Update Vcs-* headers for switch to salsa.debian.org

  [ gregor herrmann ]
  * debian/watch: use uscan version 4.

 -- Jelmer Vernooij <email address hidden>  Sun, 12 Jun 2022 22:15:46 +0100

Upload details

Uploaded by:
Debian Perl Group
Uploaded to:
Sid
Original maintainer:
Debian Perl Group
Architectures:
all
Section:
perl
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Oracular release universe perl
Noble release universe perl
Mantic release universe perl
Lunar release universe perl

Builds

Kinetic: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libcriticism-perl_1.02-3.dsc 2.1 KiB 004148a44597c23f904dae455b92a85a065beb2647d25ad5784e8782d77060e6
libcriticism-perl_1.02.orig.tar.gz 14.8 KiB 962a1e8602621118d8b031283cc1220561d166894ce206d9d0ecf0049dd83975
libcriticism-perl_1.02-3.debian.tar.xz 2.1 KiB 5c140260807128215f4a4863a45ea2cf324b1de8d2e87b6a22bb949d4b93d2af

Available diffs

No changes file available.

Binary packages built by this source

libcriticism-perl: 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.