FUPPES

From Hurlster Wiki
Jump to navigation Jump to search

General Build Instructions

For most *nix distributions all that is required generally is:

$ svn co https://fuppes.svn.sourceforge.net/svnroot/fuppes/trunk fuppes
$ cd fuppes/
$ autoreconf -vfi
$ ./configure
$ make
$ make install

And then run using fuppes to start in normal mode or fuppesd to start it in daemon mode. Some systems require the final step to be run in superuser mode (depending on where the --prefix option points to.

Important Note: If you are using a Debian based distro, such as Ubuntu, or a Red Hat based distro such as Fedora, then make sure you install the -dev versions of the dependencies or else ./configure will not recognize them and the desired functionality will not be enabled.

Update Sources (Get the most recent fuppes)

To update your local copy to the last available revision simply run:

$ cd fuppes/
$ svn update
$ make
$ make install

And you will once again have the latest version of fuppes. (NOTE: If the result of the svn update is the same revision as you were already on then you do not need to perform and more steps, nothing has changed and therefore the make's are redundant)

General Troubleshooting

The first troubleshooting step is to always make sure that you have the most recent version of fuppes. If you are not sure it you do then please update your sources as mentioned above.

Gnome Applet Support

If you configure fuppes with gnome-applet support (--enable-gnome-panel-applet) you must also set the prefix to /usr (--prefix=/usr) in order to get the applet files installed in the correct directories.

cannot open shared object file

(This is mainly for Debian based systems but may work for more)

Libraries are placed in /usr/local/lib; if this is not already in your LD_LIBRARY_PATH you will get this:

root@fs1:~# fuppes
fuppes: error while loading shared libraries: libfuppes.so.0: cannot open shared object file: No such file or directory

To fix this, tell ubuntu to also look for libraries in /usr/local/lib:

echo "include /usr/local/lib" >> /etc/ld.so.conf && ldconfig

Now you should be able to run fuppes OK.

plugin X could not be loaded

If you get an error saying that any plugin cannot be found when you run fuppes they try this:

$ cd fuppes/
$ ./src/fuppes --plugin-dir src/pligins/.libs/

Running 'make install' should avoid the need for this completely.


Config files

1. instead of creating a default fuppes.cfg on the first startup fuppes now comes with a default fuppes.cfg that get's installed under $sysconfdir/etc/fuppes by runnung "make install". So you may want to configure fuppes with ./configure --prefix=/usr --sysconfdir=/etc


2. you still can override the fuppes.cfg (and all others) in $sysconfdir/etc with a fuppes.cfg in ~/.fuppes (the old location)


3. the config is split up into some smaller files

  • each device settings has it's own configuration in $sysconfdir/etc/fuppes/devices
  • each virtual folder layout has it's own configuration in $sysconfdir/etc/fuppes/vfolders
  • use the fuppes.cfg to map renderers to a certain device/vfolder combination by ip od mac


4. the vfolder configuration has lost some weight.

  • the "device" and "enabled" attributes are gone. instead of "device" we just use the file name and enabling/disabling a layout is now done by fuppes.cfg
  • the "create_references" attribute is gone. We always create references and that's it. If you don't understand what I'm writing about just forget it. All you need to know; It was a confusing and unnecessary setting and now it' gone.
  • there are new properties that you can use

These changes should make it a lot easier for users to share their device settings. Just drop in the device configuration and map it to a renderer.


Database

Well, it has changed a lot. And now you can use mysql instead of sqlite if you want.


Everything else

  • FAM (File Alteration Monitoring) should finally work correctly on Linux
  • Metadata is no longer read the moment a file is added but a few seconds after the last FAM event
  • files are automatically inserted in all enabled virtual folder layouts (no need to rebuild the vfolder layout anymore)
  • ...