The EventLog library aims to be a replacement of the simple syslog() API
provided on UNIX systems. The major difference between EventLog and syslog
is that EventLog tries to add structure to messages.
Where you had a simple non-structrured string in syslog() you have a
combination of description and tag/value pairs.
EventLog provides an interface to build, format and output an event record.
The exact format and output method can be customized by the administrator
via a configuration file.
Add a reminder to expire this port when sysutils/syslog-ng310 is
expired. syslog-ng311 and subsequent ports use their own copy of
eventlog. This is a packaging decision made by Balabit, the authors
of syslog-ng.
Cleanup $() variables in ports Makefiles.
Mostly replace with ${}, but sometime, replace with $$() because it is
what was intended in the first place. (I think.)
Sponsored by: Absolight
Eradicate USE_GNOME=pkgconfig
While here:
- Trim headers
- Convert USE_GMAKE to USES=gmake
- Convert USE_GNOME=gnomehack to USES=pathfix
- Convert USE_PERL5 to USES=perl5
Update 0.2.10 --> 0.2.12.
Take on maintainership of this port.
Approved by: Ivan Lago <ivan.lago@ifom-ieo-campus.it> (Maintainer)
Prodded by: Peter Czanik <czanik@balabit.hu> (Upline)
The EventLog library aims to be a replacement of the simple syslog() API
provided on UNIX systems. The major difference between EventLog and syslog
is that EventLog tries to add structure to messages.
Where you had a simple non-structrured string in syslog() you have a
combination of description and tag/value pairs.
EventLog provides an interface to build, format and output an event record.
The exact format and output method can be customized by the administrator
via a configuration file.
PR: ports/105370
Submitted by: Ivan Lago <ivan.lago at ifom-ieo-campus.it>
