pool/perl-Log-Log4perl
SHA256
2
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Accepting request 375948 from devel:languages:perl:autoupdate

Browse Source 
automatic update

OBS-URL: https://build.opensuse.org/request/show/375948
OBS-URL: https://build.opensuse.org/package/show/devel:languages:perl/perl-Log-Log4perl?expand=0&rev=28
This commit is contained in:
P. Janouch 2016-03-21 10:13:37 +00:00 committed by Git OBS Bridge
parent 373a13c96a
commit 295d96d7c0
4 changed files with 40 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Log-Log4perl-1.46.tar.gz
View File

@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:31011a17c04e78016e73eaa4865d0481d2ffc3dc22813c61065d90ad73c64e6f
size 278058

3
Log-Log4perl-1.47.tar.gz Normal file
View File

@ -0,0 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:9001dded011226538b9a50c7856815bb0dba72a1e6218fdcaba56f651356b96f
size 278780

22
perl-Log-Log4perl.changes
View File

@ -1,3 +1,25 @@
-------------------------------------------------------------------
Sun Mar 20 10:16:58 UTC 2016 - coolo@suse.com
- updated to 1.47
see /usr/share/doc/packages/perl-Log-Log4perl/Changes
1.47 (2016/03/17)
* (ms) [rt.cpan.org #102647] Slaven Rezic fixed a test
case for file permissions
* (ms) Fixed synopsis code in Log::Log4perl::Appender::DBI,
reported by Chris Collins.
* (ms) Added suggestion by Dylan Doxey to test for both MSWin32 and
cygwin to detect windows-like systems for which tests need
to be skipped.
* (ms) [rt.cpan.org #110915] Fixed "Redundant argument in sprintf"
warning caused by DateFormat.pm with %d{Z} placeholders,
reported by Alexander Hartmaier.
* (ms) [rt.cpan.org #110512] Felix Ostmann fixed a broken error
message raised when a boolean filter can't be found.
* (ms) All hash traversals in Config.pm now done via "sort keys"
to make sure we can reliably reproduce potential problems.
-------------------------------------------------------------------
Sun Sep 6 08:46:05 UTC 2015 - coolo@suse.com

36
perl-Log-Log4perl.spec
View File

@ -1,7 +1,7 @@
#
# spec file for package perl-Log-Log4perl
#
# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany.
# Copyright (c) 2016 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,7 +17,7 @@
Name: perl-Log-Log4perl
Version: 1.46
Version: 1.47
Release: 0
%define cpan_name Log-Log4perl
Summary: Log4j implementation for Perl
@ -30,8 +30,8 @@ BuildArch: noarch
BuildRoot: %{_tmppath}/%{name}-%{version}-build
BuildRequires: perl
BuildRequires: perl-macros
BuildRequires: perl(File::Path) >= 2.0606
Requires: perl(File::Path) >= 2.0606
BuildRequires: perl(File::Path) >= 2.060600
Requires: perl(File::Path) >= 2.060600
%{perl_requires}
%description
@ -41,7 +41,7 @@ of your system from the outside. It implements the widely popular
*For a detailed tutorial on Log::Log4perl usage, please read*
the http://www.perl.com/pub/a/2002/09/11/log4perl.html manpage
http://www.perl.com/pub/a/2002/09/11/log4perl.html
Logging beats a debugger if you want to know what's going on in your code
during runtime. However, traditional logging packages are too static and
@ -50,23 +50,17 @@ generate a flood of log messages in your log files that won't help you.
'Log::Log4perl' is different. It allows you to control the number of
logging messages generated at three different levels:
* *
* At a central location in your system (either in a configuration file or in
the startup code) you specify _which components_ (classes, functions) of
your system should generate logs.
At a central location in your system (either in a configuration file or
in the startup code) you specify _which components_ (classes, functions)
of your system should generate logs.
* You specify how detailed the logging of these components should be by
specifying logging _levels_.
* *
You specify how detailed the logging of these components should be by
specifying logging _levels_.
* *
You also specify which so-called _appenders_ you want to feed your log
messages to ("Print it to the screen and also append it to /tmp/my.log")
and which format ("Write the date first, then the file name and line
number, and then the log message") they should be in.
* You also specify which so-called _appenders_ you want to feed your log
messages to ("Print it to the screen and also append it to /tmp/my.log")
and which format ("Write the date first, then the file name and line
number, and then the log message") they should be in.
This is a very powerful and flexible mechanism. You can turn on and off
your logs at any time, specify the level of detail and make that dependent
@ -85,7 +79,7 @@ re-read even while it's running!
%prep
%setup -q -n %{cpan_name}-%{version}
find . -type f -print0 | xargs -0 chmod 644
find . -type f ! -name \*.pl -print0 | xargs -0 chmod 644
%build
%{__perl} Makefile.PL INSTALLDIRS=vendor