Hello community, here is the log from the commit of package perl-Log-Any for openSUSE:Factory checked in at 2015-04-15 16:25:59 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/perl-Log-Any (Old) and /work/SRC/openSUSE:Factory/.perl-Log-Any.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "perl-Log-Any" Changes: -------- --- /work/SRC/openSUSE:Factory/perl-Log-Any/perl-Log-Any.changes 2013-12-03 10:42:57.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.perl-Log-Any.new/perl-Log-Any.changes 2015-04-15 16:26:00.000000000 +0200 @@ -1,0 +2,92 @@ +Tue Apr 14 21:20:56 UTC 2015 - [email protected] + +- updated to 1.032 + see /usr/share/doc/packages/perl-Log-Any/Changes + + 1.032 2015-03-26 17:23:37-04:00 America/New_York + + - no changes from 1.031 + + 1.031 2015-03-26 06:08:17-04:00 America/New_York (TRIAL RELEASE) + + [Fixed] + + - Log::Any::Adapter::Test passed through all constructor arguments, + which could be fatal when mocking adapters without all key-value + pairs (like Log::Any::Adapter::File); now this only passes through + the category and ignores other parameters when used as an + adapter class override. + + 1.03 2015-01-01 22:39:41-05:00 America/New_York + + [Changed] + + - Log::Any::Proxy concatenates arguments to basic logging functions + with a space character before passing them to adapters as a single + string. This ensures consistency across adapters that handle + multiple arguments differently. + + 1.02 2014-12-28 07:06:49-05:00 America/New_York + + [Fixed] + + - Some adapters relied on Log::Any::Adapter::Util also loading + Log::Any so this behavior has been restored. + + 1.01 2014-12-26 22:25:13-05:00 America/New_York + + [Fixed] + + - 'numeric_level' was not exported properly from + Log::Any::Adapter::Util + + 1.00 2014-12-25 22:04:13-05:00 America/New_York + + [Added] + + - Logging now goes via a Log::Any::Proxy object instead of directly to + an adapter. This allows easy customization of the message production. + + - File, Stdout, and Stderr adapters now support a minimum + log level parameter. + + [Changed] + + - Removed dead code from Log::Any::Adapter::Base; particularly this + was the formatting code, since this is now handled by + Log::Any::Proxy. + + [Fixed] + + - File will flock the handle when writing (if flock is avaiable). + + - Won't die if adapters aren't loadable modules as long as they + provide a constructor. This allows using private adapters + defined in another file. + + [Documented] + + - Revised docs for creating adapters + + - Fixed typos and improved docs for Log::Any::Adapter::Util; removed + stub docs for modules that didn't need it. + + [Deprecated] + + - Deprecated some methods in Log::Any::Adapter::Util + + [Internal] + + - Merged Log-Any and Log-Any-Adapter distributions; reduces code + duplication and ensures Log::Any and adapter framework stay in sync + + - Eliminates all non-core dependencies (as of Perl 5.8.1), including + Capture::Tiny, Devel::GlobalDestruction and Guard + + 0.92 2014-12-15 07:12:38-05:00 America/New_York (TRIAL RELEASE) + + 0.91 2014-12-14 22:13:09-05:00 America/New_York (TRIAL RELEASE) + + 0.90 2014-12-12 17:08:22-05:00 America/New_York (TRIAL RELEASE) + +------------------------------------------------------------------- Old: ---- Log-Any-0.15.tar.gz New: ---- Log-Any-1.032.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ perl-Log-Any.spec ++++++ --- /var/tmp/diff_new_pack.b7Xz43/_old 2015-04-15 16:26:00.000000000 +0200 +++ /var/tmp/diff_new_pack.b7Xz43/_new 2015-04-15 16:26:00.000000000 +0200 @@ -1,7 +1,7 @@ # # spec file for package perl-Log-Any # -# Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany. +# Copyright (c) 2015 SUSE LINUX 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,41 +17,58 @@ Name: perl-Log-Any -Version: 0.15 +Version: 1.032 Release: 0 %define cpan_name Log-Any Summary: Bringing loggers and listeners together License: Artistic-1.0 or GPL-1.0+ Group: Development/Libraries/Perl Url: http://search.cpan.org/dist/Log-Any/ -Source: http://www.cpan.org/authors/id/J/JS/JSWARTZ/%{cpan_name}-%{version}.tar.gz +Source: http://www.cpan.org/authors/id/D/DA/DAGOLDEN/%{cpan_name}-%{version}.tar.gz BuildArch: noarch BuildRoot: %{_tmppath}/%{name}-%{version}-build BuildRequires: perl BuildRequires: perl-macros -#BuildRequires: perl(Capture::Tiny) -#BuildRequires: perl(Log::Any) -#BuildRequires: perl(Log::Any::Adapter) -#BuildRequires: perl(Log::Any::Adapter::Core) -#BuildRequires: perl(Log::Any::Adapter::Null) -#BuildRequires: perl(Log::Any::Adapter::Test) -#BuildRequires: perl(Log::Any::Test) -#BuildRequires: perl(Log::Dispatch) %{perl_requires} %description -'Log::Any' allows CPAN modules to safely and efficiently log messages, -while letting the application choose (or decline to choose) a logging -mechanism such as 'Log::Dispatch' or 'Log::Log4perl'. +'Log::Any' provides a standard log production API for modules. the +Log::Any::Adapter manpage allows applications to choose the mechanism for +log consumption, whether screen, file or another logging mechanism like the +Log::Dispatch manpage or the Log::Log4perl manpage. + +Many modules have something interesting to say. Unfortunately there is no +standard way for them to say it - some output to STDERR, others to 'warn', +others to custom file logs. And there is no standard way to get a module to +start talking - sometimes you must call a uniquely named method, other +times set a package variable. + +This being Perl, there are many logging mechanisms available on CPAN. Each +has their pros and cons. Unfortunately, the existence of so many mechanisms +makes it difficult for a CPAN author to commit his/her users to one of +them. This may be why many CPAN modules invent their own logging or choose +not to log at all. + +To untangle this situation, we must separate the two parts of a logging +API. The first, _log production_, includes methods to output logs (like +'$log->debug') and methods to inspect whether a log level is activated +(like '$log->is_debug'). This is generally all that CPAN modules care +about. The second, _log consumption_, includes a way to configure where +logging goes (a file, the screen, etc.) and the code to send it there. This +choice generally belongs to the application. + +A CPAN module uses 'Log::Any' to get a log producer object. An application, +in turn, may choose one or more logging mechanisms via the +Log::Any::Adapter manpage, or none at all. -'Log::Any' has a very tiny footprint and no dependencies beyond Perl 5.6, +'Log::Any' has a very tiny footprint and no dependencies beyond Perl 5.8.1, which makes it appropriate for even small CPAN modules to use. It defaults to 'null' logging activity, so a module can safely log without worrying about whether the application has chosen (or will ever choose) a logging mechanism. -The application, in turn, may choose one or more logging mechanisms via -Log::Any::Adapter. +See the http://www.openswartz.com/2007/09/06/standard-logging-api/ manpage +for the original post proposing this module. %prep %setup -q -n %{cpan_name}-%{version} @@ -70,6 +87,6 @@ %files -f %{name}.files %defattr(-,root,root,755) -%doc Changes LICENSE README tidyall.ini +%doc Changes CONTRIBUTING.mkdn LICENSE README %changelog ++++++ Log-Any-0.15.tar.gz -> Log-Any-1.032.tar.gz ++++++ ++++ 4986 lines of diff (skipped)
