From clamav-devel-bounces@lists.clamav.net Mon Mar 30 14:31:10 2009 Return-Path: X-Original-To: list@tad.clamav.net Delivered-To: list@tad.clamav.net X-Virus-Scanned: Debian amavisd-new at tad.clamav.net Received: from tad.clamav.net ([127.0.0.1]) by localhost (tad.clamav.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A5Z6YPLBJclG; Mon, 30 Mar 2009 14:31:09 +0200 (CEST) Received: from tad.clamav.net (localhost.localdomain [127.0.0.1]) by tad.clamav.net (Postfix) with ESMTP id B7A8916C1AF; Mon, 30 Mar 2009 14:31:07 +0200 (CEST) X-Original-To: clamav-devel@tad.clamav.net Delivered-To: clamav-devel@tad.clamav.net X-Virus-Scanned: Debian amavisd-new at tad.clamav.net Received: from tad.clamav.net ([127.0.0.1]) by localhost (tad.clamav.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ERdBPFS0qu52 for ; Mon, 30 Mar 2009 14:31:04 +0200 (CEST) Received: from cupid.digitalfuture.it (static-217-133-237-204.clienti.tiscali.it [217.133.237.204]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by tad.clamav.net (Postfix) with ESMTP id 68C5316C082 for ; Mon, 30 Mar 2009 14:31:04 +0200 (CEST) Message-ID: <49D0BB80.8080107@digitalfuture.it> Date: Mon, 30 Mar 2009 14:30:56 +0200 From: aCaB User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: ClamAV Development References: In-Reply-To: Subject: Re: [Clamav-devel] Suggestion - decouple functionality upgrade from API changes X-BeenThere: clamav-devel@lists.clamav.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: ClamAV Development List-Id: ClamAV Development List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: clamav-devel-bounces@lists.clamav.net Errors-To: clamav-devel-bounces@lists.clamav.net 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