http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8190
--- Comment #6 from Jonathan Druart <[email protected]> --- (In reply to comment #2) > Right now every warn in code makes patch fail QA (I know that first > hand ;-) and it seems to me it's easier to just put warn instead of > > C4::Logger->new->debug( "this used to be warn" ); Just $log->debug("my debug message"); In fact, a lot of warn in Koha are not a debug message. I think each warn have to be replaced with his right level. But your are right, we can have a thought about this. (A simple method is to map into your favorite editor the string "warn" with a call to the debug method of Logger ;) (In reply to comment #3) > I had a thought about this. Would it be possible to have the logging module > serve dual purposes, for both debug logging and for action_logs logging? Hum, I had already this idea and I think it is not a good one :) First, it would take a lot of disk space. To process the results, we will have to grep a huge number of lines of data. Then, we oblige users to keep all of their Koha log. We will depend of an other source of data (currently, we only have the DB). Imo processing time would be very increased. (In reply to comment #4) > Perhaps also take a look at Log4Perl > http://search.cpan.org/~mschilli/Log-Log4perl-1.37/lib/Log/Log4perl.pm I had a look at several perl logging modules. My conclusion is LogLite is the easier for what we need into Koha. In any case, since we have a Koha::Utils::Logger used in Koha, it is easy to replace this module with another ;) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
