If you were with your eyes on this, you may already know that on the compiz community forum the first stable version of Compiz-Fusion, that is 0.6.0 has been released. But if you happen to use debian unstable, aka sid, you may want to add to your repositories that of “shame“, whose packages work well, in my case with the speedy, shiny, always up-to-date rolling-release distro called sidux.
This release includes:
Compiz Plugin sets (plugins are split into three packages according to their
usefulness and stability):
compiz-fusion-plugins-main:
This is the main plugin set, fully supported and providing the most
significant features. Check the list of plugins included in this
pack, with descriptions on http://wiki.compiz-fusion.org/PluginsMain
compiz-fusion-plugins-extra:
This is the extra plugin set, fully supported and providing less
significant features. Check the list of plugins included in this
set, with descriptions http://wiki.compiz-fusion.org/PluginsExtra
compiz-fusion-plugins-unsupported:
This is the unsupported plugin set, which components should work but
aren’t officially supported by the development team. Check the list
of plugins included in this pack, with descriptions on
http://wiki.compiz-fusion.org/PluginsUnsupported
compiz-manager:
Compiz-manager is a wrapper script intended to start compiz with the
appropriate arguments for the environment in use. It is intended
both for use in distributions and by end-users who install Compiz
Fusion in other ways than using their distribution’s packages.
compiz-bcop:
BCOP is a code generator that provides an easy way to handle plugin
options by generating parts of the plugin code directly from the xml
metadata file. It is used for most of the Compiz Fusion plugins.
libcompizconfig:
CompizConfig is an alternative configuration system for
compiz that provides the following features :
- Automatic plugin list generation.
- Import/Export of the current configuration.
- Configuration profiles.
- Parsing of Compiz metadata files to provide an easy to use API for
configuration managers.
- Conflict handling for plugins and actions.
- Support for different configuration storage backends.
- Desktop environment integration. If a backend provides desktop
environment integration, then Compiz will share the keybindings
and settings with the default desktop environment window manager
like metacity or kwin.
- Its own Compiz configuration plugin “ccp” to provide all features
of libcompizconfig with compiz.
compizconfig-backend-kconfig:
The kconfig backend for CompizConfig. It uses the KDE configuration
system to store the compiz configuration and provides integration into
the KDE desktop environment.
compizconfig-backend-gconf:
The gconf backend for CompizConfig. It uses the GNOME configuration
system and provides integration into the GNOME desktop environment.
compizconfig-python:
Python bindings for the compizconfig library.
compizconfig-settings-manager (a.k.a. ccsm):
A fully featured Python/GTK based settings manager for the CompizConfig
system, targeted to power users.
Stay tuned, this is a winner environment and my guess is: the best is yet to come.
