[1292_2] s/module/backend/ [library]

src/lib/datasrc/Makefile.am

@@ -7,7 +7,7 @@ AM_CPPFLAGS += $(SQLITE_CFLAGS)
 
 AM_CXXFLAGS = $(B10_CXXFLAGS)
 
-pkglibexecdir = $(libexecdir)/@PACKAGE@/modules
+pkglibexecdir = $(libexecdir)/@PACKAGE@/backends
 
 datasrc_config.h: datasrc_config.h.pre
 	$(SED) -e "s|@@PKGLIBEXECDIR@@|$(pkglibexecdir)|" datasrc_config.h.pre >$@

src/lib/datasrc/factory.h

@@ -115,11 +115,11 @@ private:
 /// easy recognition and to reduce potential mistakes.
 /// For example, the sqlite3 implementation has the type 'sqlite3', and the
 /// derived filename 'sqlite3_ds.so'
-/// The value of type can be a specific loadable module; if it already ends
+/// The value of type can be a specific loadable library; if it already ends
 /// with '.so', the loader will not add '_ds.so'.
 /// It may also be an absolute path; if it starts with '/', nothing is
-/// prepended. If it does not, the loadable module will be taken from the
-/// installation library directory.
+/// prepended. If it does not, the loadable library will be taken from the
+/// libexec/backends/ installation directory.
 /// \note When 'B10_FROM_BUILD' is set in the environment, the build
 ///       directory is used instead of the install directory.
 ///

src/lib/datasrc/tests/Makefile.am

@@ -105,8 +105,8 @@ EXTRA_DIST += testdata/rwtest.sqlite3
 EXTRA_DIST += testdata/diffs.sqlite3
 
 # For the factory unit tests, we need to specify that we want
-# the loadable modules from the build tree, and not from the
-# installation directory. Therefore we build it into a separate
+# the loadable backend libraries from the build tree, and not from 
+# the installation directory. Therefore we build it into a separate
 # binary, and call that from check-local with B10_FROM_BUILD set.
 # Also, we only want to do this when static building is not used,
 # since it will cause various troubles with static link such as