Adding compatibility with ubuntu lucid.

The Ubuntu Lucid has package libmenu-cache-dev, not libmenu-cache1-dev
so added as alternative to be compatible with it.
Correcting dependency for libfm-data: Replaces to Conflicts.

the 'Replaces: libfm0' on libfm-data doesn't enforce removal of libfm0
nor libfm1 but both libfm0 and libfm1 contain the same files as the
libfm-data package so 'Conflicts:' was added instead.
Corrections for symbols files.

Files debian/libfm-dbg.symbols and debian/libfm-dev.symbols have no
usage. Files debian/libfm-gtk3.symbols and debian/libfm3.symbols has
wrong symbols.
Updated debian/libfm3.symbols and debian/libfm-gtk3.symbols to the
symbols and required versions up to libfm 1.0.1 version.
Package libfm-dev split into libfm-dev and libfm-doc.

User may want do not have HTML docs but only header files.
HTML docs moved into separate package which is recommended by libfm-dev.
Adding libfm-gtk-data package - libfm-gtk3 will crash without it.

Without libfm-gtk-data (library independent) package libfm-gtk will crash.
And there we have two choices:
1) to have libfm-gtk3 dependent on libfm-gtk-bin;
2) to add libfm-gtk-data package.
libfm-gtk-bin package contains optional binary application
which never required nor somehow related to libfm. The only
relation is libfm-pref-apps application is linked against libfm.
Therefore have libfm-gtk3 package to be dependent on it is
completely wrong and inappropriate.
So only good choice is to add the libfm-gtk-data package.
Adding suggestion from libfm-gtk3 onto libfm-gtk-bin.

The libfm-gtk-bin contains optional application which uses libfm-gtk
library and may be useful so suggestion will hint users to install and use it.
Renaming libfm-gtk-bin package into libfm-tools.

package name libfm-gtk-bin isn't appropriate as it contains only an
optional application which is linked against libfm-gtk but isn't
related to libfm-gtk otherwise. So it renamed into libfm-tools (see
Debian Policy recommendations).
Adding version check for libfm-data dependency from libfm3.

libfm-data package contains translated strings which are changed
from older versions therefore messages will be partially translated
if installed version of libfm-data is older than libfm3.
This patch adds version requirement to force update of libfm-data.
Moving /usr/share/apport/package-hooks into libfm-data package.

/usr/share/apport/package-hooks isn't appropriate for the library
package (library package should contain only library itself, see
Debian Policy) so it moved into libfm-data package.
Fixing wrong package name in dh_strip arguments.

The package mentioned in dh_strip arguments was libfm1 while
actual package name is libfm3 but libfm1 does not exist.
Moving Depends: libfm-gtk3 into Recommends, in packages libfm-dbg and libfm-dev.

Some of users may never want use gtk libs but only libfm itself and enforce
to install all gtk stuff (libgtk and other dependencies) if it isn't
needed by user is completely wrong, and Debian Policy states that
unneded dependencies are bad.
Adding postinst script for libfm-dev.

The 1.0.2~ versions of libfm have a symlink supplied and resolving that
is required on the upgrade (that is dpkg issue, see Debian Policy for
details why it should be done for supplied symlinks).
Adding a package libfm-gtk3-3 with libfm-gtk3.so.X.X.X library.

The libfm since version 1.0.2~ may be build against libgtk-3 as well.
Since applications built against libgtk-3 cannot be linked with
libraries that are built against libgtk-2, that requires coexistance
of both versions of library - one against Gtk+-2.0 and one against Gtk+-3.0.
This patch adds a package libfm-gtk3-3 which is built against Gtk+-3.0.
Adding '-f' option for autoreconf.

Original source tarball may contain configure script which differs
in parts related to libtool and that leads to failure. Error message
says configure script should be rebuilt. Without -f autoreconf doesn't
rebuild configure from source tarball so -f is needed to do it.

The most probably that problem should be reported to libtool or
autoconf upstream.

This patch adds a workaround on that issue.
debian/rules: Enable parallel building

See `man dh` and `man dpkg-buildflags` for more information. The user
has to enable for example in `/etc/dpkg/buildflags.conf` how many jobs
can be build in parallel.
Updating changelog file to actual upstream version (NMU).