From: Tim Pease <tim.pease@...>
Date: 2007-01-17T04:29:24+09:00
Subject: Re: [ANN] Logging 0.1.0

On 1/16/07, Jonas Pfenniger <zimbatm@oree.ch> wrote:
> 2007/1/15, Tim Pease <tim.pease@gmail.com>:
> >
> > On 1/15/07, Jonas Pfenniger <zimbatm@oree.ch> wrote:
> > > Yes ! A decent ruby logger. I was waiting for this since a long time.
> > >
> >
> > Hmmm ... I would download the code first and poke around ... kick the
> > wheels.  But thanks for the exuberance :)
>
>
> No problem, I've tried to contact the Log4r developper regarding some bugs
> and I'm happy that the project revives. I have a big project and once I've
> added Log4r support, it became much easier to debug.
>
> > Are you going to fix the syslog adapter ? In Log4r, when you used syslog,
> > it
> > > would change the error level and reporting methods. It's pretty
> > annoying.
> > >
> >
> > Sure. The field is wide open at the moment. I'm looking for
> > suggestions / requests from developers.
> >
> > My thought on syslog is to require a mapping from the user that maps
> > the defined logging levels to the syslog logging levels. If the user
> > has not defined any logging levels, then the syslog levels become the
> > default (i.e. the current Log4r behavior).
>
>
> Ok, I'll let you know on this. In the meantime, can you check why the
> loggging gem is not available ? I think you should contact rubyforge people.
> It's maybe related to the fact that somebody else already released a
> logging.tgz file, as package names are locked to a project for security
> reasons.
>

They are doing some security audits / updates on RubyForge right now.
Gems are not being migrated over for distribution until they are done
with this.  You can manually download the gem and install it if you
would like to tinker.

http://rubyforge.org/frs/?group_id=2870

Blessings,
TwP