This is isolated as a feature request from Bug #5592, reported by Buchan Milne <bgmilne@mandriva.org>. Quote from bug #5592: At present, both shared libraries and plugins shipped with samba (3.0.x and 3.2.x) are installed to the location provided to configure with the --with-libdir option. It would be preferable to be able to specify the locations independently. For example, Linux distributions may want to have the shared libraries in a location that can be found by the library loader, but may not necessarily want ldconfig to have to look at plugins. (As an example, OpenLDAP by default puts shared libraries such as libldap in %{_libdir} and other server-specific shared objects such as backends, overlays, and slapi plugins in %{_libdir}/openldap)
I think I would greatly ease things for packages to have a modules dir for the shared modules and a libs dir for the published shared libraries. Most packagers of linux distributions currently move or manually re-install the libs from /usr/lib/samba to /usr/lib... Michael
I have committed to v3-devel, the new samba3 development brancht, a set of patches that implement the separation of the libdir into libdir (for shared and static libraries) and modulesdir (for shared modules like the vfs, pdb and idmap modules, codepages, and so on). Not that I have removed the "--with-libdir" configure switch which did the same as the standard --libdir switch. Instead, I have now added the --with-modulesdir switch that defaults to ${libdir} in standard mode and to ${libdir}/samba in fhs mode. Michael
this has been released with 3.3.0 --> FIXED