090116 Compiz-Fusion 0.7.8 [VL 6.0]

[caitlyn]

M0E-lnx has packaged an updated set of Compiz-Fusion packages for VL 6.0.

Package:  ccsm-0.7.8-i586-1vl60.tlz
MD5:  277edb87ab28abff7bc47fcde4dfc281
Package Size:  418K

Sources:  http://vectorlinux.osuosl.org/veclinux-6.0/source/testing/x-apps/ccsm

Code:

ccsm: CCSM (CompizConfig Settings Manager)
ccsm:
ccsm: CCSM, short for CompizConfig Settings Manager, is a configuration tool
ccsm: for Compiz Fusion. It is used to configure the many plugins included
ccsm: in Compiz and Compiz Fusion, as well as the use of various profiles
ccsm: and intergrating better with existing desktop settings.
ccsm: CCSM uses the CompizConfig compiz configuration system.
ccsm:
ccsm:
ccsm:
ccsm:

Package:  compiz-0.7.8-i686-1vl60.tlz
MD5:  2dbf648ab067308eeca71999fd28ebd9
Package Size:  396K
Installed Size: 2110K

Sources:  http://vectorlinux.osuosl.org/veclinux-6.0/source/testing/x-apps/compiz

Code:

compiz: Compiz (3D compositing window manager)
compiz:
compiz: Compiz is a compositing  window  manager  that  uses  3D  graphics
compiz: acceleration via OpenGL. It provides various new graphical effects
compiz: and features on any desktop environment, including Gnome and KDE.
compiz:
compiz:
compiz:
compiz:                        http://compiz.org

Package:  compiz-bcop-0.7.8-i586-1vl60.tlz
MD5:  0fba0cd593f4c414aa5c0d7e412e2b70
Package Size:  16K
Installed Size:  110K

Sources:  http://vectorlinux.osuosl.org/veclinux-6.0/source/testing/x-apps/compiz-bcop

Code:

ompiz-bcop: compiz-bcop (BCOP is a code generator)
compiz-bcop:
compiz-bcop: BCOP is a code generator that provides an easy way to handle
compiz-bcop: plugin options by generating parts of the plugin code directly
compiz-bcop: from the xml metadata file.  It is used for most of the Compiz
compiz-bcop: Fusion plugins.
compiz-bcop:
compiz-bcop:
compiz-bcop:
compiz-bcop:
compiz-bcop:

Package:  compiz-fusion-plugins-extra-0.7.8-i586-1vl60.tlz
MD5:  648ac7a1599f9f0c0f97f3635eb243db
Package Size:  2160K
Installed Size:  6360K

Sources:  http://vectorlinux.osuosl.org/veclinux-6.0/source/testing/x-apps/compiz-fusion-plugins-extra

Code:

compiz-fusion-plugins-extra: compiz-fusion-plugins-extra  (extra plugins)
compiz-fusion-plugins-extra:
compiz-fusion-plugins-extra: compiz fusion extra plugins
compiz-fusion-plugins-extra:
compiz-fusion-plugins-extra:
compiz-fusion-plugins-extra:
compiz-fusion-plugins-extra:
compiz-fusion-plugins-extra:
compiz-fusion-plugins-extra:
compiz-fusion-plugins-extra:
compiz-fusion-plugins-extra:

Package:  compiz-fusion-plugins-main-0.7.8-i586-1vl60.tlz
MD5:  13cb72bbe04c6e784acbfc046eaf3a41
Package Size:  828K
Installed Size:  5230K

Sources:  http://vectorlinux.osuosl.org/veclinux-6.0/source/testing/x-apps/compiz-fusion-plugins-main

Code:

compiz-fusion-plugins-main: compiz-fusion-plugins-main (supported plugins)
compiz-fusion-plugins-main:
compiz-fusion-plugins-main: compiz-fusion-plugins-main is the main plugin
compiz-fusion-plugins-main: package for Compiz Fusion.
compiz-fusion-plugins-main:
compiz-fusion-plugins-main:
compiz-fusion-plugins-main:
compiz-fusion-plugins-main:
compiz-fusion-plugins-main:
compiz-fusion-plugins-main:
compiz-fusion-plugins-main:

Package:  compiz-fusion-plugins-unsupported-0.7.8-i586-1vl60.tlz
MD5:  10f384a2a4793abf33a037250054f73a
Package Size:  459K
Installed Size:  2920K

Sources:  http://vectorlinux.osuosl.org/veclinux-6.0/source/testing/x-apps/compiz-fusion-plugins-unsupported

Code:

compiz-fusion-plugins-unsupported: compiz-fusion-plugins-unsupported
compiz-fusion-plugins-unsupported:
compiz-fusion-plugins-unsupported: This is the unsupported plugin set. All
compiz-fusion-plugins-unsupported: of the components should work, but aren't
compiz-fusion-plugins-unsupported: officially supported by the development
compiz-fusion-plugins-unsupported: team.
compiz-fusion-plugins-unsupported:
compiz-fusion-plugins-unsupported:
compiz-fusion-plugins-unsupported:
compiz-fusion-plugins-unsupported:
compiz-fusion-plugins-unsupported:

Package:  compizconfig-python-0.7.8-i586-1vl60.tlz
MD5:  cdd28b3a5ac6b7bd6a2bafeef978e663
Package Size:  38K
Installed Size:  150K

Sources:  http://vectorlinux.osuosl.org/veclinux-6.0/source/testing/x-apps/compizconfig-python

Code:

compizconfig-python: compizconfig-python (Python bindings for compiz config)
compizconfig-python:
compizconfig-python: Python bindings for the compiz config library.
compizconfig-python:
compizconfig-python:
compizconfig-python:
compizconfig-python:
compizconfig-python:
compizconfig-python:
compizconfig-python:
compizconfig-python:

Package:  emerald-0.7.8-i586-1vl60.tlz
MD5:  b3b562fd98dbc5853b0f4e9a3134d4d2
Package Size:  260K
Installed Size:  1210K

Sources:  http://vectorlinux.osuosl.org/veclinux-6.0/source/testing/x-apps/emerald

Code:

emerald: emerald (Emerald Window Decorator)
emerald:
emerald: The Emerald Window Decorator is a custom window decorator.
emerald: Emerald allows for all sorts of different configurations and layouts
emerald: of buttons, look, title bars and frames. Emerald Window Decorator is
emerald: completely independent of any desktop,and you specify your own
emerald: themes to use for it.
emerald:
emerald:
emerald:
emerald:

Package:  emerald-themes-0.5.2-i586-1vl60.tlz
MD5:  e42426c7f389b376dbcac4ffbb654126
Package Size:  1146K
Installed Size:  2370K

Sources:  http://vectorlinux.osuosl.org/veclinux-6.0/source/testing/x-apps/emerald-themes

Code:

emerald-themes: emerald-themes (Extra themes for the emerald)
emerald-themes:
emerald-themes: Extra themes for the emerald window decorator.
emerald-themes:
emerald-themes:
emerald-themes:
emerald-themes:
emerald-themes:
emerald-themes:
emerald-themes:
emerald-themes:

Package:  fusion-icon-0.01-i586-1vl60.tlz
MD5:  69380e8f82157025f51089ae72a40859
Package Size:  35K
Installed Size:  170K

Sources:  http://vectorlinux.osuosl.org/veclinux-6.0/source/testing/x-apps/fusion-icon

Code:

fusion-icon: fusion-icon (fusion icon system tray tool)
fusion-icon:
fusion-icon: fusion icon is a system tray tool to manage compiz fusion
fusion-icon:
fusion-icon:
fusion-icon:
fusion-icon:
fusion-icon:
fusion-icon:
fusion-icon:
fusion-icon:

Package:  libcompizconfig-0.7.8-i586-1vl60.tlz
MD5:  f5c54456caa06bf05cdec8ae3d84f58a
Package Size:  53K
Installed Size:  210K

Sources:  http://vectorlinux.osuosl.org/veclinux-6.0/source/testing/x-apps/libcompizconfig

Code:

libcompizconfig: libcompizconfig (a configuration system for compiz)
libcompizconfig:
libcompizconfig: CompizConfig is an alternative configuration system for
libcompizconfig: compiz.
libcompizconfig:
libcompizconfig:
libcompizconfig:
libcompizconfig:
libcompizconfig:
libcompizconfig:
libcompizconfig:

Package:  simple-ccsm-0.7.8-i586-1vl60.tlz
MD5:  339e4a21edbce6b2061bdf9b10b3c854
Package Size:  42K
Installed Size:  330K

Sources:  http://vectorlinux.osuosl.org/veclinux-6.0/source/testing/x-apps/simple-ccsm

Code:

simple-ccsm: simple-ccsm (CompizConfig Settings Manager simple version)
simple-ccsm:
simple-ccsm: CCSM, short for CompizConfig Settings Manager, is a configuration
simple-ccsm: tool for Compiz Fusion. It is used to configure the many plugins
simple-ccsm: included in Compiz and Compiz Fusion, as well as the use of
simple-ccsm: various profiles and intergrating better with existing desktop
simple-ccsm: settings.
simple-ccsm:
simple-ccsm: CCSM uses the CompizConfig compiz configuration system.
simple-ccsm:
simple-ccsm:

After testing these packages please stop back here and let us know how they work for you.

[stretchedthin]

I gave it a go on VL rc3 and ended up with a big white spinning cube.
I've got a feeling it is not the fault of the packages, however, because I had the same result with the
previous packages.

I started with a fresh install before trying MOE-inx packages, I then installed all the packages mentioned in this thread.

Here's terminal output ...
ken:$ fusion-icon
 * Detected Session: xfce
 * Searching for installed applications...
 * Using the GTK Interface
 * Starting Compiz
 ... executing: compiz --replace --sm-disable --ignore-desktop-hints ccp
Which all seems pretty normal.  I am going to reinstall my Nvidia video drivers as "The white cube" when googled seems to be a pretty common problem related to drivers.

[stretchedthin]

I reinstalled my Nvidia drivers 180.22, and I'm happy to report the packages worked great.  Wonder why, VL6.0 rc3 did not install video drivers correctly.
Ken

[Joe1962]

Just installed these on 6.0 Standard RC4 and they seem to work ok.

[caitlyn]

We've had great reports about these packages all over the forum, not just in this thread.  As a result these packages have all been moved to the extra repository.  Thanks to M0E-lnx and everyone who tested packages.

[tomh38]

Thanks to M0E-lnx and caitlyn.  Compiz-Fusion works great on my machine.

I have an nvidia geforce 7300 agp card, and a 1.6 Ghz Sempron processor.  Not exactly low-end, but definitely not recent either.  This doohicky doesn't even slow it down on Xfce.

Tom

[Joe1962]

A little packaging issue here... the gsb fusion-icon package shows up as an upgrade on gslapt ("mark all upgrades"), due to the version number: 0.1.0 vs. 0.01

[M0E-lnx]

Yeah... I didn't know how to address that, there is really no 0.1.0 release of fusion-icon... it's just kept under version control... so unless we increase the version number, that will always be the case.

if no other deps are pulled by the gsb package (which I doubt) it should technically be a harmless change

[Joe1962]

Ok, as long as the gsb package doesn't break anything...

[rbistolfi]

Malloc added some features to slapt-get to give priorities to a repo over another one, maybe we could use them to prevent any upgrade from gsb.

[caitlyn]

Malloc added some features to slapt-get to give priorities to a repo over another one, maybe we could use them to prevent any upgrade from gsb.

If that is now possible that would definitely be a good thing to implement in the final release of VL 6.0.

[uelsk8s]

Malloc added some features to slapt-get to give priorities to a repo over another one, maybe we could use them to prevent any upgrade from gsb.

If that is now possible that would definitely be a good thing to implement in the final release of VL 6.0.

It is possible, and already implemented.
We still may need to figure out the best way to use it for our repo's

57. How do I assign priorities to my package sources?

 The source priority feature is intended for keeping installed packages closely
 synchronised with a trusted repository, rather than upgrading based on package
 version numbers.  This can be useful for tracking the patches which are
 applied to official Slackware releases, or for following Slackware-current,
 where package version numbers are occasionally regressed due to stability
 issues or for other reasons.  Another use for this feature is where the user
 maintains a local repository of customised packages which are to be used in
 preference to those on the public mirrors.

 Each SOURCE can be a assigned a priority level, by appending :{PRIORITY} to
 the source URI.  For example:

  SOURCE={url}:DEFAULT    is the default, lowest priority
  SOURCE={url}:OFFICIAL   assigns more weight, used to denote official sources
  SOURCE={url}:PREFERRED  assigns even more weight to this source
  SOURCE={url}:CUSTOM     highest priority, for your custom package source

 PRIORITY of DEFAULT gives the usual slapt-get behaviour, whereby packages are
 upgraded based on their version numbers.  A package from a source with the
 default priority will upgrade the installed package only if the package from
 the source has a higher version number.  This is effectively never used but is
 included for completeness.

 The priorities of OFFICIAL, PREFERRED, and CUSTOM allow the packages from a
 mirror to be tracked more closely.  A package from a source with a priority
 higher than DEFAULT will "upgrade" the installed package whenever the version
 strings differ, regardless of whether this is an upgrade or a downgrade in
 terms of version number comparison.  Where a package is available in different
 versions from several different sources, the package from the source with the
 greatest priority will be used for upgrade.  Version numbers are only
 considered in the event of a tie between two packages from sources with the
 same priority.

 Packages within the patches sub directory always have a slightly increased
 priority of those within the rest of the package source.  This is particularly
 useful for tracking official Slackware patches.  So any packages in /patches
 are assigned +1 priority to the package sources priority.

 The example slapt-getrc in the source tarball or in the slapt-get directory
 within /usr/doc/ provides example usage of package source priority assignment.

 If you do not care for the priority assignment, you can remove the priority
 attributes from your sources (if present, or never add them if not).

[rbistolfi]

I think if we add :OFFICIAL to each VL source and :DEFAULT to gsb (for completeness ) would work. I will test it when I get home after work. 

[uelsk8s]

I think if we add :OFFICIAL to each VL source and :DEFAULT to gsb (for completeness ) would work. I will test it when I get home after work. 

I am testing it here now. It does work, BUT because not all pkgs on iso are in repo yet, gslapt wants to downgrade them.

[caitlyn]

It seems the solution is to make sure that all of those packages are in the repo before VL 6.0 final releases.  This does seem like the best solution to the general problems with gsb to me.  FWIW, I've been slowly replacing gsb packages with updated VL packages as time permits but I doubt I'll ever get to all of them.