Files
perl-Module-Versions-Report/perl-Module-Versions-Report.spec

81 lines
2.7 KiB
RPMSpec

#
# spec file for package perl-Module-Versions-Report
#
# Copyright (c) 2011 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.
# Please submit bugfixes or comments via http://bugs.opensuse.org/
#
# norootforbuild
Name: perl-Module-Versions-Report
%define real_name Module-Versions-Report
Summary: Report versions of all modules in memory t
Url: http://search.cpan.org/perldoc?Module::Versions::Report
Group: Development/Libraries/Perl
License: Artistic License
Version: 1.06
Release: 1
Source: %{real_name}-%{version}.tar.gz
BuildRequires: perl-macros
BuildRoot: %{_tmppath}/%{name}-%{version}-build
%{perl_requires}
%description
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 "Perl 5". 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's
2.27". "Is that my module or XML::Parser?" "XML::Parser." "OK, and what about
my module's version?" "Ohyeah. 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 the all modules in memory, and noting
the version of each (for modules that defined a $VERSION, at least).
Author:
-------
Sean M. Burke, <sburke@cpan.org>
%prep
%setup -n %{real_name}-%{version}
%build
perl Makefile.PL
make %{?jobs:-j%jobs}
%check
make test
%install
%perl_make_install
%perl_process_packlist
%perl_gen_filelist
%clean
rm -rf %{buildroot}
%files -f %{name}.files
%defattr(-, root, root)
%doc ChangeLog README MANIFEST
%changelog