On Fri, 21 Aug 2015, Thomas D. wrote:
Hi,
Rainer Gerhards wrote:
Well, liblognorm-1.1.1 to 1.1.2 is a *minor* bump according to the
version number.
Well, we (rsyslog project) still use the "rsyslog traditional
versioning scheme" for this version of liblognorm, and this means
1.1.2 was just not yet ready for 1.2, because all 1.1 goals were not
reached. It doesn't mean its a bugfixing relaese only. That's of
course different from your expectation, but no point in arguing on it
-- that's how it is. In v2, we can change that, and will probably move
to the new rsyslog scheme (a new release every 6 weeks with
incrementing x version (as in 2.x.y)).
OK, we have applied a mask for liblognorm-1.1.2.
Would be nice if you could ping me just *before* liblognorm-2 release so
I can verify proper SONAMEs... Thanks!
right now, the v2-experimental branch creates the liblognorm.so.3.0.0
I think this is incorect, but I'm not sure what is correct. While I could go
research it, I'm going to be a little lazy and explain things to you and rely on
your expertise :-)
this library is backwards compatible, so if you link it to liblognorm.so.2.0.0
everything works.
as I understand it, there are some new APIs available that were not in the old
one.
what is the correct soname to use?
David Lang
_______________________________________________
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.
