| 1 |
Source: liblog-log4perl-perl |
| 2 |
Maintainer: Debian Perl Group <[email protected]> |
| 3 |
Uploaders: gregor herrmann <[email protected]> |
| 4 |
Section: perl |
| 5 |
Testsuite: autopkgtest-pkg-perl |
| 6 |
Priority: optional |
| 7 |
Build-Depends: debhelper-compat (= 13) |
| 8 |
Build-Depends-Indep: libdbd-csv-perl <!nocheck>, |
| 9 |
libdbd-sqlite3-perl <!nocheck>, |
| 10 |
liblog-dispatch-filerotate-perl <!nocheck>, |
| 11 |
liblog-dispatch-perl <!nocheck>, |
| 12 |
librrds-perl <!nocheck>, |
| 13 |
libxml-dom-perl <!nocheck>, |
| 14 |
perl |
| 15 |
Standards-Version: 4.6.1 |
| 16 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/liblog-log4perl-perl |
| 17 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/liblog-log4perl-perl.git |
| 18 |
Homepage: https://metacpan.org/release/Log-Log4perl |
| 19 |
Rules-Requires-Root: no |
| 20 |
|
| 21 |
Package: liblog-log4perl-perl |
| 22 |
Architecture: all |
| 23 |
Multi-Arch: foreign |
| 24 |
Depends: ${misc:Depends}, |
| 25 |
${perl:Depends} |
| 26 |
Recommends: libipc-shareable-perl, |
| 27 |
liblog-dispatch-perl |
| 28 |
Suggests: libdbd-csv-perl, |
| 29 |
liblog-dispatch-filerotate-perl, |
| 30 |
librrds-perl, |
| 31 |
libxml-dom-perl |
| 32 |
Description: Perl port of the widely popular log4j logging package |
| 33 |
Log::Log4perl is a pure Perl port of the widely popular Apache/Jakarta |
| 34 |
log4j library for Java. In the spirit of log4j, Log::Log4perl |
| 35 |
addresses the shortcomings of typical ad-hoc or homegrown logging |
| 36 |
systems by providing three mechanisms to control the amount of data |
| 37 |
being logged and where it ends up at: |
| 38 |
* Levels allow you to specify the priority of log |
| 39 |
messages. Low-priority messages are suppressed when the system's |
| 40 |
setting allows for only higher-priority messages. |
| 41 |
* Categories define which parts of the system you want to enable |
| 42 |
logging in. Category inheritance allows you to elegantly reuse |
| 43 |
and override previously defined settings of different parts in the |
| 44 |
category hierarchy. So, at a central location in your system (either |
| 45 |
in a configuration file or in the startup code) you may specify which |
| 46 |
components (classes, functions) of your system should generate logs. |
| 47 |
* Appenders allow you to choose which output devices the log data |
| 48 |
is being written to, once it clears the previously listed |
| 49 |
hurdles. |