Re: [Gluster-devel] RPM re-structuring

[Bharata B Rao]

On Wed, Aug 14, 2013 at 1:37 PM, Anand Avati <address@hidden> wrote:
>
> Actually this *wasnt* what we discussed. glusterfs-api was supposed to
> depend on glusterfs-libs *ONLY*. This is because it has a linking (hard)
> relationship with glusterfs-libs, and glusterfs.rpm is only a run-time
> dependency - everything here is dlopen()ed.

I just wanted to see what is the user experience of having glusterfs
runtime dependency not met, by starting QEMU after deleting
storage/client.so from the system. (equivalent of not having glusterfs
rpm)

address@hidden qemu]# ./x86_64-softmmu/qemu-system-x86_64 --enable-kvm
-nographic -m 2048 -smp 4 -drive
file=gluster://bharata/test/F17,if=virtio
qemu-system-x86_64: -drive file=gluster://bharata/test/F17,if=virtio:
Gluster connection failed for server=bharata port=0 volume=test
image=F17 transport=tcp
Segmentation fault (core dumped)

I know one shouldn't do this, but glusterfs-api not depending on
glusterfs could result in many such unintended uses and associated
issues.

Regards,
Bharata.