On Thu, Feb 13, 2014 at 6:26 PM, Michael Biebl <[email protected]> wrote:

> Hi Rainer,
>
>
> so I've looked at 7.6.0 today which got a hard dependency on
> liblogging-stdlog, which means I'll have to package that for Debian as
> well.
>
> Preparing the package for liblogging, and specifically the
> liblogging-stdlog binary package, I haven't found any clues what to
> put into the package short and long description.
> The .pc file only says:
>
> standard logging library for C
>

well, actually that's what it intends to become ;)

But I agree it's not a good description today. How about

"an enhanced replacement for the syslog() API [with admin-configurable
destinations]"

Note that 1.0.1 is a shim. I am currently working on the "real" version. If
you check the git, you'll see quite a bit of activity.


>
> The homepage http://www.liblogging.org/ isn't that helpful either
> regarding what liblogging (and its components) is supposed to be.
>
> Can you give a oneline description of the liblogging-stdlog library
> and a short paragraph going into more detail?
>

Short paragraph could probably be:

---
Think of liblogging-stdlog as the next version of the syslog(3) API. It
retains the easy semantics, but makes the API more sophisticated "behind
the scenes" with better support for multiple threads and flexibility for
different log destinations. It provides seperation of concerns, where the
application developer is responsible only for logging, but the
administrator can select the log diver, e.g. go to syslog, file or systemd
journal. In that sense, it is similar to log4j.
---

Does this work for you? Again, the 1.0.1 version *does not* fit into that
description. But 1.1 will, and I am actively working on it.

Rainer
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to