[Gluster-devel] Determining libgfapi/glusterfs version

[Anand Avati]

This looks more like a compile time feature check than runtime. The
PKG_CONFIG() api number which had the initial set of QEMU requirements was
3 (i.e, PKG_CONFIG(..,glusterfs-api>=3,..). The new updates for Samba
requirements has api number 4. Depending on whether discard support makes
it before the next release (and api numbers gets published) or not,
glfs_discard() would either be available in 4 or 5. Also, you might also
want to add a second AC_CHECK_FUNC macro in configure.ac to be doubly sure.

Avati


On Mon, Jun 3, 2013 at 1:52 AM, Vijay Bellur <vbellur at redhat.com> wrote:

> On 05/31/2013 10:10 PM, Bharata B Rao wrote:
>
>> Hi,
>>
>> What is the best way to determine if I am running (or linked to) a
>> particular version of libgfapi/glusterfs ?
>>
>
> This would be a runtime determination, right? We are evolving versions for
> libgfapi that is independent of the package version.
>
> http://review.gluster.org/#/c/**4932/<http://review.gluster.org/#/c/4932/>
>
>
>
>
>> Requirement: If I want to support the use of glfs_discard() from QEMU,
>> I should be doing it only if QEMU is linked to a version of libgfapi
>> that supports glfs_discard().
>>
>>
> Maybe a new api glfs_get_version() can be evolved to determine libgfapi
> capability at runtime?
>
> Regards,
> Vijay
>
>
>
>
> ______________________________**_________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> https://lists.nongnu.org/**mailman/listinfo/gluster-devel<https://lists.nongnu.org/mailman/listinfo/gluster-devel>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20130603/d68fc7f1/attachment-0001.html>