File: control

package info (click to toggle)
libmodule-versions-report-perl 1.02-1
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 60 kB
  • ctags: 9
  • sloc: perl: 58; makefile: 44
file content (30 lines) | stat: -rw-r--r-- 1,507 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
Source: libmodule-versions-report-perl
Section: perl
Priority: optional
Maintainer: Stephen Quinney <stephen@jadevine.org.uk>
Build-Depends-Indep: perl (>= 5.6.0-16), debhelper (>= 4.0.0)
Standards-Version: 3.6.1.0

Package: libmodule-versions-report-perl
Architecture: all
Depends: perl (>= 5.6.0-16)
Description: Report versions of all modules in memory
 The author says: "I often get email from someone reporting a bug in a
 module I've written. I email back, asking what version of the module
 it is, what version of Perl on what OS, and sometimes what version of
 some relevent third library (like XML::Parser). They reply, saying
 "Perl5". I say "I need the exact version, as reported by 'perl -v'".
 They tell me. And I say "I, uh, also asked about the version of my 
 module and XML::Parser [or whatever]". They say "Oh yeah. It is 2.27".
 "Is that my module or XML::Parser?" "XML::Parser." "OK, and what
 about my module's version?" "Oh yeah. That's 3.11." By this time,
 days have passed, and what should have been a simple operation --
 reporting the version of Perl and relevent modules, has been
 needlessly complicated".
 .
 This module is for simplifying that task. If you add "use
 Module::Versions::Report;" to a program (especially handy if your
 program is one that demonstrates a bug in some module), then when the
 program has finished running, you well get a report detailing all the
 modules in memory, and noting the version of each (for modules that
 defined a $VERSION, at least).