File: control

package info (click to toggle)
libppix-documentname-perl 0.001003-1.1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 272 kB
  • sloc: perl: 251; makefile: 2
file content (34 lines) | stat: -rw-r--r-- 1,277 bytes parent folder | download | duplicates (2)
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
Source: libppix-documentname-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: gregor herrmann <gregoa@debian.org>
Section: perl
Testsuite: autopkgtest-pkg-perl
Priority: optional
Build-Depends: debhelper (>= 9)
Build-Depends-Indep: libppi-perl,
                     perl
Standards-Version: 4.1.1
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-perl/packages/libppix-documentname-perl.git
Vcs-Git: https://anonscm.debian.org/git/pkg-perl/packages/libppix-documentname-perl.git
Homepage: https://metacpan.org/release/PPIx-DocumentName

Package: libppix-documentname-perl
Architecture: all
Depends: ${misc:Depends},
         ${perl:Depends},
         libppi-perl
Description: utility to extract a name from a PPI Document
 PPIx::DocumentName contains a few utilities for extracting a "name" out of an
 arbitrary Perl file.
 .
 Typically, this is the module name, in the form:
 .
  package Foo
 .
 However, it also supports extraction of an override statement in the form:
 .
  # PODNAME: OverrideName::Goes::Here
 .
 which may be more applicable for documents that lack a package statement, or
 the package statement may be "wrong", but they still need the document parsed
 under the guise of having a name (for purposes such as POD).