[rsyslog] rsyslog 1.19.8 released
rgerhards at hq.adiscon.com
Fri Sep 28 20:11:20 CEST 2007
I need to prepare for german astronomy day tomorrow, so brief ;)
The point was that a single package (RPM or whatever) can be pre-build
for the core and the mysql functionality. I think the configure options
do not help with that. Or do they?
> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Michael Biebl
> Sent: Friday, September 28, 2007 6:07 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] rsyslog 1.19.8 released
> 2007/9/28, Rainer Gerhards <rgerhards at hq.adiscon.com>:
> > Hi Michael,
> > as I have blogged, I am not yet sure about how to handle the
> > I am also consulting with Autotools experts, any advise is
> > Two packages seem useful, especially when more plugins become
> > (I myself think about email and a couple of other databases). Many
> > also do not like the idea of having to have libmysql present on the
> > system just to install rsyslog - with a core package and the plugin,
> Well, this is not quite true. If you don't want to have mysql support,
> you could just use --disable-mysql. This way you don't have to have
> mysql installed.
> Such a --enable/disable-feature option could be added for any plugin
> that will be added in the future.
> > those can only install the core (and that will probably the majority
> > cases).
> > What I have not yet found - and I have very limited expertise in
> > area - is how to do that in the best possible way.
> I do have quite some experience with autotools. So if any help is
> needed, I'll gladly offer it.
> > release 1 of it). So, in the medium to long term, ommysql *will* be
> > separate project - maybe one with a different maintainer, as I am no
> > mysql guy.
> This actually is a valid argument for splitting it off.
> But to reiterate what I posted earlier: For the plugins shipped
> directly by the rsyslog project, I'd prefer to have them in a single
> tarball with configure options to turn them on/off and as long as you
> are the maintainer of the mysql output plugin its more convenient to
> keep them in one project. Why not make the split when the plugin
> interface is stable, other output plugins are available (and we have
> more experience how to handle them) and a external maintainer for
> ommysql is found?
> I hope this doesn't sound too negative. I generally like the idea of
> having a plugin interface, but I only fear that splitting things up
> prematurely without knowing how it develops, will complicate things
> (and probably destabilize).
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> rsyslog mailing list
More information about the rsyslog