Message ID | 20160716182009.23643-2-alex@pompo.co |
---|---|
State | New |
Headers | show |
Thanks. I was in the process of packaging log4perl also, you beat me to it. On 17/07/16 04:20, Alex Sassmannshausen wrote: > * gnu/packages/perl.scm (perl-log-any): New variable. > --- > gnu/packages/perl.scm | 31 +++++++++++++++++++++++++++++++ > 1 file changed, 31 insertions(+) > > diff --git a/gnu/packages/perl.scm b/gnu/packages/perl.scm > index aed2a61..486dbc2 100644 > --- a/gnu/packages/perl.scm > +++ b/gnu/packages/perl.scm > @@ -2939,6 +2939,37 @@ either uses the first module it finds or throws an error.") > versa.") > (license (package-license perl)))) > > +(define-public perl-log-any > + (package > + (name "perl-log-any") > + (version "1.040") > + (source > + (origin > + (method url-fetch) > + (uri (string-append "mirror://cpan/authors/id/D/DA/DAGOLDEN/Log-Any-" > + version ".tar.gz")) > + (sha256 > + (base32 > + "0r1q7cclgwl24gzdnjzvd8y0r7j17dngjk492x35w198zhdj2ncp")))) > + (build-system perl-build-system) > + (home-page "http://search.cpan.org/dist/Log-Any") > + (synopsis "Bringing loggers and listeners together") > + (description "Log::Any provides a standard log production API for > +modules. Log::Any::Adapter allows applications to choose the mechanism for log > +consumption, whether screen, file or another logging mechanism like > +Log::Dispatch or Log::Log4perl. > + > +A CPAN module uses Log::Any to get a log producer object. An application, in > +turn, may choose one or more logging mechanisms via Log::Any::Adapter, or none > +at all. > + > +Log::Any has a very tiny footprint and no dependencies beyond Perl 5.8.1, A reference to the specific Perl version is a bit out of place, no? Maybe 'no dependencies beyond Perl itself'. Otherwise LGTM. > +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.") > + (license (package-license perl)))) > + > (define-public perl-log-report-optional > (package > (name "perl-log-report-optional")
diff --git a/gnu/packages/perl.scm b/gnu/packages/perl.scm index aed2a61..486dbc2 100644 --- a/gnu/packages/perl.scm +++ b/gnu/packages/perl.scm @@ -2939,6 +2939,37 @@ either uses the first module it finds or throws an error.") versa.") (license (package-license perl)))) +(define-public perl-log-any + (package + (name "perl-log-any") + (version "1.040") + (source + (origin + (method url-fetch) + (uri (string-append "mirror://cpan/authors/id/D/DA/DAGOLDEN/Log-Any-" + version ".tar.gz")) + (sha256 + (base32 + "0r1q7cclgwl24gzdnjzvd8y0r7j17dngjk492x35w198zhdj2ncp")))) + (build-system perl-build-system) + (home-page "http://search.cpan.org/dist/Log-Any") + (synopsis "Bringing loggers and listeners together") + (description "Log::Any provides a standard log production API for +modules. Log::Any::Adapter allows applications to choose the mechanism for log +consumption, whether screen, file or another logging mechanism like +Log::Dispatch or Log::Log4perl. + +A CPAN module uses Log::Any to get a log producer object. An application, in +turn, may choose one or more logging mechanisms via Log::Any::Adapter, or none +at all. + +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.") + (license (package-license perl)))) + (define-public perl-log-report-optional (package (name "perl-log-report-optional")