Mailing List Archive

Suggestion - decouple functionality upgrade from API changes
The latest 0.95 release brings a new flevel 41 with the previous one
from 0.94.2 being 38. Unfortunately it looks like libclamav 0.95 isn't
a drop-in replacement for 0.94.2, but brings along changes to the API.
I'm sure there are good reasons for that, but for anyone using the
clamav library directly, the new flevel is not available without local
changes to the API.
In the future, might it be possible to make new flevels available
without changing the API ? Through a wrapper or some such?


/Per Jessen, Zürich

_______________________________________________
http://lurker.clamav.net/list/clamav-devel.html
Please submit your patches to our Bugzilla: http://bugs.clamav.net
Re: Suggestion - decouple functionality upgrade from API changes [ In reply to ]
Per Jessen wrote:
> The latest 0.95 release brings a new flevel 41 with the previous one
> from 0.94.2 being 38. Unfortunately it looks like libclamav 0.95 isn't
> a drop-in replacement for 0.94.2, but brings along changes to the API.
> I'm sure there are good reasons for that, but for anyone using the
> clamav library directly, the new flevel is not available without local
> changes to the API.
> In the future, might it be possible to make new flevels available
> without changing the API ? Through a wrapper or some such?

Hi Per,

One of the issues that 0.95 addresses is API/ABI stability across revisions.
Please take a look at the new API and feel free to suggest anything
could help to limit the issue even more.

Cheers,
-aCaB
_______________________________________________
http://lurker.clamav.net/list/clamav-devel.html
Please submit your patches to our Bugzilla: http://bugs.clamav.net