File: control

package info (click to toggle)
libtest-distribution-perl 2.00-5
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, stretch
  • size: 176 kB
  • ctags: 38
  • sloc: perl: 252; makefile: 5
file content (41 lines) | stat: -rw-r--r-- 1,847 bytes parent folder | download
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
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
Source: libtest-distribution-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: Jose Luis Rivas <ghostbar@debian.org>,
           gregor herrmann <gregoa@debian.org>
Section: perl
Testsuite: autopkgtest-pkg-perl
Priority: extra
Build-Depends: debhelper (>= 9),
               libmodule-build-perl
Build-Depends-Indep: perl,
                     libfile-find-rule-perl,
                     libtest-pod-perl,
                     libtest-pod-coverage-perl,
                     libpod-coverage-perl
Standards-Version: 3.9.6
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-perl/packages/libtest-distribution-perl.git
Vcs-Git: git://anonscm.debian.org/pkg-perl/packages/libtest-distribution-perl.git
Homepage: https://metacpan.org/release/Test-Distribution

Package: libtest-distribution-perl
Architecture: all
Depends: ${misc:Depends},
         ${perl:Depends},
         libfile-find-rule-perl,
         libtest-pod-perl,
         libtest-pod-coverage-perl,
         libpod-coverage-perl
Description: perform tests on all modules of a distribution
 When using Test::Distribution in a test script, it goes through all the
 modules in your distribution, checks their POD, checks that they compile ok
 and checks that they all define a $VERSION.
 .
 This module also performs a number of tests on the distribution itself. It
 checks that your files match your SIGNATURE file if you have one. It checks
 that your distribution isn't missing certain 'core' description files. It
 checks to see you haven't missed out listing any pre-requisites in Makefile.PL
 .
 It defines its own testing plan, so you usually don't use it in conjunction 
 with other Test::* modules in the same file. It's recommended that you just 
 create a one-line test script as shown in the SYNOPSIS above. However, there 
 are options.