Hello community, here is the log from the commit of package perl-Devel-Cover for openSUSE:Factory checked in at 2012-05-31 17:08:12 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/perl-Devel-Cover (Old) and /work/SRC/openSUSE:Factory/.perl-Devel-Cover.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "perl-Devel-Cover", Maintainer is "" Changes: -------- --- /work/SRC/openSUSE:Factory/perl-Devel-Cover/perl-Devel-Cover.changes 2012-01-04 07:26:29.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.perl-Devel-Cover.new/perl-Devel-Cover.changes 2012-05-31 17:08:15.000000000 +0200 @@ -1,0 +2,36 @@ +Wed May 30 11:42:39 UTC 2012 - [email protected] + +- updated to 0.87 + - Major documentation overhaul (Pau Amma). + - Cleanup Data::Dumper usage (localise settings) (Olivier Mengué) (rt 76531). + - Ignore more generated filenames - Moose and Template Toolkit. + - Improve results for chained logical operators. + - Officially support 5.16.0. + + - Add all coverage criteria to the Vim report. + + - Add customisable thresholds to HTML reports (Xavier Caron). + - Improve Vim report. + + - Add Vim report (based on discussion with Tatsuhiko Miyagawa). + + - Prefer JSON::XS for faster operation (Audrey Tang (唐鳳)). + - Rework testing framework (Xavier Caron). + + - Do not distribute MYMETA.json (Olivier Mengué) (rt 75883). + + - Fix up dzil release process. + + - Don't be so noisy with Moose code. + - Move to Dist:Zilla (Christian Walde). + - Test against 5.14.2 and 5.15.2 - 5.15.8. + - Select gcov2perl from the same directory as cover. + - Print warnings to STDERR so $SIG{__WARN__} isn't called (Christian Walde). + - Manage coverage reporting errors before an exec (Daisuke Maki). + - Don't run fork tests on Windows (Christian Walde). + - Add more documentation about cover --test (Kirk Kimmel). + - Remove race conditions around mkdir. + - Add travis config file. + - Add word "Warning" to MD5 digest message. + +------------------------------------------------------------------- Old: ---- Devel-Cover-0.79.tar.gz New: ---- Devel-Cover-0.87.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ perl-Devel-Cover.spec ++++++ --- /var/tmp/diff_new_pack.MtIWrR/_old 2012-05-31 17:08:16.000000000 +0200 +++ /var/tmp/diff_new_pack.MtIWrR/_new 2012-05-31 17:08:16.000000000 +0200 @@ -1,7 +1,7 @@ # # spec file for package perl-Devel-Cover # -# Copyright (c) 2011 SUSE LINUX Products GmbH, Nuernberg, Germany. +# Copyright (c) 2012 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 @@ -17,11 +17,11 @@ Name: perl-Devel-Cover -Version: 0.79 +Version: 0.87 Release: 0 %define cpan_name Devel-Cover Summary: Code coverage metrics for Perl -License: GPL-1.0+ or Artistic-1.0 +License: Artistic-1.0 or GPL-1.0+ Group: Development/Libraries/Perl Url: http://search.cpan.org/dist/Devel-Cover/ Source: http://www.cpan.org/authors/id/P/PJ/PJCJ/%{cpan_name}-%{version}.tar.gz @@ -29,6 +29,35 @@ BuildRequires: perl BuildRequires: perl-macros BuildRequires: perl(Test::Warn) +#BuildRequires: perl(DC::Test::Dist) +#BuildRequires: perl(DC::Test::Dist::M1) +#BuildRequires: perl(Devel::Cover) +#BuildRequires: perl(Devel::Cover::Branch) +#BuildRequires: perl(Devel::Cover::Condition) +#BuildRequires: perl(Devel::Cover::Condition_and_2) +#BuildRequires: perl(Devel::Cover::Condition_and_3) +#BuildRequires: perl(Devel::Cover::Condition_or_2) +#BuildRequires: perl(Devel::Cover::Condition_or_3) +#BuildRequires: perl(Devel::Cover::Condition_xor_4) +#BuildRequires: perl(Devel::Cover::Criterion) +#BuildRequires: perl(Devel::Cover::DB) +#BuildRequires: perl(Devel::Cover::DB::Digests) +#BuildRequires: perl(Devel::Cover::DB::File) +#BuildRequires: perl(Devel::Cover::DB::IO) +#BuildRequires: perl(Devel::Cover::DB::Structure) +#BuildRequires: perl(Devel::Cover::Dumper) +#BuildRequires: perl(Devel::Cover::Inc) +#BuildRequires: perl(Devel::Cover::Pod) +#BuildRequires: perl(Devel::Cover::Report::Html_minimal) +#BuildRequires: perl(Devel::Cover::Statement) +#BuildRequires: perl(Devel::Cover::Subroutine) +#BuildRequires: perl(Devel::Cover::Test) +#BuildRequires: perl(Devel::Cover::Time) +#BuildRequires: perl(Devel::Cover::Truth_Table) +#BuildRequires: perl(Devel::Cover::Web) +#BuildRequires: perl(Module1) +#BuildRequires: perl(Template) >= 2.00 +#BuildRequires: perl(Template::Provider) Requires: perl(Test::Warn) Recommends: perl(JSON::PP) Recommends: perl(Parallel::Iterator) @@ -36,7 +65,7 @@ Recommends: perl(Pod::Coverage) >= 0.06 Recommends: perl(Pod::Coverage::CountParents) Recommends: perl(PPI::HTML) >= 1.07 -Recommends: perl(Template) >= 2 +Recommends: perl(Template) >= 2.00 Recommends: perl(Test::Differences) %{perl_requires} @@ -47,40 +76,46 @@ tests to create to increase coverage. Code coverage can be considered as an indirect measure of quality. -I consider this software to have an alpha status. By that I mean that I -reserve the right to alter the interface in a backwards incompatible manner -without incrementing the major version number. I specifically do not mean -that this software is full of bugs or missing key features. Although I'm -making no guarantees on that front either. In short, if you are looking for -code coverage software for Perl, you have probably come to the end of your -search. For more of my opinions on this subject, see -http://pjcj.sytes.net/notes/2007/03/14#alpha +Although it is still being developed, Devel::Cover is now quite stable and +provides many of the features to be expected in a useful coverage tool. -Code coverage data are collected using a pluggable runops function which -counts how many times each op is executed. These data are then mapped back -to reality using the B compiler modules. There is also a statement -profiling facility which needs a better backend to be really useful. This -release also includes an experimental mode which replaces ops instead of -using a pluggable runops function. This provides a nice speed increase, but -needs better testing before it becomes the default. You probably don't care -about any of this. - -The _cover_ program can be used to generate coverage reports. - -Statement, branch, condition, subroutine, pod and time coverage information -is reported. Statement coverage data should be reasonable, although there -may be some statements which are not reported. Branch and condition -coverage data should be mostly accurate too, although not always what one -might initially expect. Subroutine coverage should be as accurate as -statement coverage. Pod coverage comes from the Pod::Coverage manpage. If -the Pod::Coverage::CountParents manpage is available it will be used -instead. Coverage data for path coverage are not yet collected. +Statement, branch, condition, subroutine, and pod coverage information is +reported. Statement coverage data should be reasonable. Branch and +condition coverage data should be mostly accurate too, although not always +what one might initially expect. Subroutine coverage should be as accurate +as statement coverage. Pod coverage comes from the Pod::Coverage manpage. +If the Pod::Coverage::CountParents manpage is available it will be used +instead. Coverage data for other criteria are not yet collected. + +The _cover_ program can be used to generate coverage reports. Devel::Cover +ships with a number of different reports including various types of HTML +output, textual reports, a report to display missing coverage in the same +format as compilation errors and a report to display coverage information +within the Vim editor. + +It is possible to add annotations to reports, for example you could add a +column to an HTML report showing who last changed a line, as determined by +git blame. Some annotation modules are shipped with Devel::Cover and you +can easily create your own. The _gcov2perl_ program can be used to convert gcov files to 'Devel::Cover' -databases. +databases. This allows you to display your C or XS code coverage together +with your Perl coverage, or to use any of the Devel::Cvoer reports to +display your C coverage data. + +You may find that the coverage results don't match your expectations. This +could be due to a bug in Devel::Cover, but code coverage can be unintuitive +to newcomers, and especially so with Perl, so you may want to reconsider +your expectations as well. -You may find that the results don't match your expectations. I would -imagine that at least one of them is wrong. +Code coverage data are collected by replacing perl ops with functions which +count how many times the ops are executed. These data are then mapped back +to reality using the B compiler modules. There is also a statement +profiling facility which should not be relied on. For proper profiling use +Devel::NYTProf. Previous versions of Devel::Cover collected coverage data +by replacing perl's runops function. It is still possible to switch to that +mode of operation, but this now gets little testing and will probably be +removed soon. You probably don't care about any of this. The most appropriate mailing list on which to discuss this module would be perl-qa. Discussion has migrated there from perl-qa-metrics which is now @@ -105,11 +140,8 @@ %perl_process_packlist %perl_gen_filelist -%clean -%{__rm} -rf %{buildroot} - %files -f %{name}.files %defattr(-,root,root,755) -%doc CHANGES cover cpancover gcov2perl README +%doc Changes docs README tests utils %changelog ++++++ Devel-Cover-0.79.tar.gz -> Devel-Cover-0.87.tar.gz ++++++ ++++ 20894 lines of diff (skipped) -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
