[syslog-ng] [PATCH] afmongodb: Support system-installed libmongo-client at configure time.

[Balazs Scheidler]

On Fri, 2011-07-01 at 14:49 +0200, Gergely Nagy wrote:
> Gergely Nagy <algernon at balabit.hu> writes:
> 
> > Gergely Nagy <algernon at balabit.hu> writes:
> >
> >> Gergely Nagy <algernon at balabit.hu> writes:
> >>
> >>> Modify configure.in to recognise a suitable version (>= 0.1.0) of the
> >>> libmongo-client library, and use it instead of the internal version if
> >>> requested so.
> >>
> >> Also, please update the internal libmongo-client to v0.1.0, released a
> >> couple of hours ago. (It is tagged v0.1.0 in the upstream git tree at
> >> git://github.com/algernon/libmongo-client.git)
> >
> > Actually, since this hasn't been done yet - I plan to release 0.1.1
> > tomorrow, which would be a better candidate: it has a few new things
> > that I plan to use in the mongodb driver in 3.4, and also fixes a
> > problem on a few platform + gcc combinations. I played too many pointer
> > games, and on a few architectures, a certain GCC version overoptimised
> > it, and the result wasn't pretty.
> >
> > That fixed, and the new stuff would be great to have in the internal
> > library.
> >
> > The NEWS file in my git tree has more info about what 0.1.1 will
> > bring. It's API and ABI compatible with 0.1.0, and so on and so forth.
> >
> > So updating to 0.1.1 would be better in the long run, as I won't have to
> > ask for another update once I get to publishing the interesting mongodb
> > stuff for 3.4 ;)
> 
> ...and today 0.1.2 is out, and here goes another ping to update the
> internal copy, if possible.
> 
> An updated MongoDB destination is available in my modules collection,
> that makes use of some of the new features that are not present in the
> internal copy yet.
> 
> The downside is that it requires glib >= 2.16, slightly newer than what
> syslog-ng requires right now, but still pretty damn old (released
> 2008-03-10, so more than 3 years old).
> 

I've updated the internal copy (just pushed out the submodules change),
however I'd be interested how much it depends on glib 2.16? Our build
systems have 2.14 deployed, and our last attempt to update that failed,
because newer glib is not trivial to compile on some of our non-Linux
platforms (at least in its pure, upstream form, sunfreeware/perzl
carries a quite recent glib).

So is the glib dependency easy to get rid of, or it is something more
inherent?

-- 
Bazsi