[debpool] Logging and error handling

[Magnus Holmgren]

On Thursday 12 April 2007 09:08, Andreas Fester wrote:
> - The original approach from Joel was, IIUC, to have a leightweight
>   implementation for a Debian pool manager, with as less dependencies
>   as possible; is this the strategy we want to continue? My opinion
>   is that it might be beneficial to use already existing packages,
>   rather than reimplementing stuff simply for minimizing dependencies.

IIUC, the goal is/was to help ports to new hardware be "self-contained", FWIW. 
I haven't figured out why it's important that packages for a particular arch, 
new or old, be distributed from machines of that arch. But I feel that for 
now it would be good if we can keep that goal.

> - This leads to my second question :) for the logging stuff,
>   it might make sense to use the already existing log4perl module
>   (liblog-log4perl-perl). I have not yet looked into it how
>   complete it is compared to log4j, but it might be worth checking it.

Please do so if you want to. Can it log to syslog as well?

One strategy might be to let the logging module collect log messages in 
addition to writing them to the log(s), starting when it's told that a new 
upload is being processed until it's done, and have it return those messages 
for inclusion in a mail. I guess that this strategy doesn't preclude any 
particular logging package from being used as a backend though.

Another thing I forgot to mention was that if "use warnings" is going to be 
really useful, we should catch them and write them to the log as well (in 
daemon mode).

-- 
Magnus Holmgren        holmgren at lysator.liu.se
                       (No Cc of list mail needed, thanks)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/debpool-devel/attachments/20070413/08bf2652/attachment.pgp