sorry for the delay. Quick update: The idea on re-introducing the "missing" API doesn't really help that much, because at an ABI level, things have still changed due to the move from json-c top libfastjson-c for returning objects. So I'll hold re-introducing old APIs until someone actually complains.
I have also a couple of issues with older autoconf or systems where autoconf-archive was not installed. I dug into that last week and have no found a good solution, which among others provides the ability to build under CentOS 5 again. I'll see that I do a new release either later today or tomorrow morning with the changed version. Rainer 2016-07-25 14:39 GMT+02:00 Rainer Gerhards <[email protected]>: > 2016-07-25 14:24 GMT+02:00 Michael Biebl <[email protected]>: >> 2016-07-25 14:16 GMT+02:00 Rainer Gerhards <[email protected]>: >>> All, >>> >>> I am exploring an option which might enable us to keep the old API >>> interface in liblognorm, which would make the benefits of v2 available >>> to some apps that insist on the old APIs for the time being. I >>> probably need a day or two to explore that and will hold the new >>> release until then. >>> >>> Given the fact that I have not yet seen any packages turn up, I think >>> we could go back to the old soname. Or should we consider this as >>> "game over"? >> >> Strictly speaking, you bump the soname when the ABI changes in an >> incompatible way. >> Also there aren't that many reverse dependencies of liblognorm afaics >> (Debian lists two: rsyslog and sagan), so please take that into >> account before you invest too much time on that. > > I dug out the conrete API in question. This is the one I am mostly > concerned about. > > https://github.com/rsyslog/liblognorm/commit/91433f98e5e0cb5be5bd4c32186f22d8bbcf3fbf > > As far as I know, this is used in a python binding, which would > probably make v2 unavailable for it. I needed to remove that API > because it is not compatible with the v2 datastructure and it's > creation. HOWEVER, at some point we decided that we need to have full > v1 compatibility and so liblognorm v2 carries the full v1 engine with > it for quite some time now. As we have that engine, the API can also > be used when a v1 rulebase is loaded. It just cannot work with the v2 > native v2 engine. I think we could return an error in that case, but > so provide a simple way to migrate to the new system. As far as I have > checked, this was the only breaking API change from v1 to v2 [but I > would check more closely if we follow that route.]. > > Any thoughts? > > Rainer > >> Michael >> >> >> >> -- >> Why is it that all of the instruments seeking intelligent life in the >> universe are pointed away from Earth? >> _______________________________________________ >> 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. _______________________________________________ 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.
