Compiz Fusion

[CCR]

Found sources at http://gitweb.opencompositing.org/
Not sure how to compile them though cuz there were no .configure file in the tarballs

Anyone up for making an ebuild of the missing goodies?

/CCR

[Mellowdrone]

I do hope, as previously stated, this indeed will be thrown into a stable 3.4 as a stable entity (I'm vouching for the mini edition considering I only have 56k. ) I'd love to give Compiz Fusion a try. I've heard any number of positive things about it, and the screenshots look amazing.

[maumike]

Found sources at http://gitweb.opencompositing.org/
Not sure how to compile them though cuz there were no .configure file in the tarballs

Anyone up for making an ebuild of the missing goodies?

/CCR

I've got both Screensaver and 3d windows using just Portage and the Sabayon overlay. What all have you emerged? I've got compiz-fusion, fusion-icon, compiz-fusion-plugins-main, compiz-fusion-plugins-unsupported, compiz-fusion-plugins-threed, and compiz-fusion-plugins-extra

[CCR]

Got the 3D windows on the cube now as i unmasked and emerged compiz-fusion-plugins-threed.
I followed the sabayon wiki how-to and i guess that threed was not yet in the keyword list.
However i still get no screensaver. Under what section of the CCSM (control panel) should it be listed?
Perhaps i need to re-emerge everything to get latest additions

/CCR

[CCR]

Re-emerged everything from scratch...still no compiz-fusion screensaver
Does anyone have a clue???

/CCR

[Darksurf]

Hey!!!

>>> Emerging (1 of 7) x11-plugins/compiz-fusion-plugins-threed-9999 to /
* checking ebuild checksums ... [ ok ]
* checking auxfile checksums ... [ ok ]
* checking miscfile checksums ... [ ok ]
>>> Unpacking source...
* git update start -->
* repository: git://anongit.opencompositing.org/fusion/plugins/3d
* local clone: /usr/portage/distfiles/git-src/compiz-fusion-plugins-threed
* committish: master
>>> Unpacked to /var/tmp/portage/x11-plugins/compiz-fusion-plugins-threed-9999/work/3d
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/x11-plugins/compiz-fusion-plugins-threed-9999/work/3d ...
convert : 3d.xml.in -> build/3d.xml
bcop'ing : build/3d.xml -> build/3d_options.h
bcop'ing : build/3d.xml -> build/3d_options.c
compiling : 3d.c -> build/3d.lo3d.c: In function 'tdPreparePaintScreen':
3d.c:223: error: 'CubeScreen' has no member named 'moMode'
3d.c:228: error: 'CubeScreen' has no member named 'moMode'
3d.c:234: error: 'CubeScreen' has no member named 'moMode'
3d.c:234: error: 'CUBE_MOMODE_MULTI' undeclared (first use in this function)
3d.c:234: error: (Each undeclared identifier is reported only once
3d.c:234: error: for each function it appears in.)
3d.c: In function 'tdInitScreen':
3d.c:999: error: 'CUBE_MOMODE_AUTO' undeclared (first use in this function)
make: *** [build/3d.lo] Error 1

!!! ERROR: x11-plugins/compiz-fusion-plugins-threed-9999 failed.
Call stack:
ebuild.sh, line 1621: Called dyn_compile
ebuild.sh, line 973: Called qa_call 'src_compile'
ebuild.sh, line 44: Called src_compile
compiz-fusion-plugins-threed-9999.ebuild, line 36: Called die

!!! make failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/x11-plugins/compiz-fusion-plugins-threed-9999/temp/build.log'.

!!! This ebuild is from an overlay: '/usr/portage/local/layman/sabayon'
localhost darksurf #

Whats with this?!?!

[Mellowdrone]

!!! ERROR: x11-plugins/compiz-fusion-plugins-threed-9999 failed.
Call stack:
ebuild.sh, line 1621: Called dyn_compile
ebuild.sh, line 973: Called qa_call 'src_compile'
ebuild.sh, line 44: Called src_compile

Whats with this?!?!

When I'd tried to install Compiz Fusion a week or two ago via the repos (following the instructions available at http://www.sabayonlinux.org/wiki/index. ... piz-Fusion ), I was given a similar error on the same file. It all had compiled well until this error was presented.

I figure I'll just wait until Sabayon 3.4 releases and hope for a better result.

[davbeck]

I have it working well... as well as beryl did when I started using it a few months ago. Most everything I ever use with beryl is working fine, so in my book compiz-fusion is an ok replacement as of current (if you can get it installed). I look toward to a stable release and 3.4 integration.

[zero]

One of the things to do "because the ebuilds pull from git repo"
is to first delete the contents of /usr/portage/distfiles/git-src

The devs are making updates through out the day so at
any given moment you may get a buggy rev. Check the
gitweb http://gitweb.opencompositing.org/?o=age before
you try and update again to see if that package has been
updated.

One of the things i do when i have a stable c-f install, is to
back it up with quickpkg. This way when i do my daily update
and it turns out buggy, i can revert to my stable backup easily.

The plugins that are not included in main, extra or, unsupported
packages are compiz-fusion-plugins-gears, compiz-fusion-plugins-threed,
compiz-fusion-plugins-screensaver, compiz-fusion-plugins-atlantis.
With the exception of gears the others are pretty stable. I believe
there is an ebuild for each of those in Sabayon overlay. If not let
me know and i can supply one to you guy's.

EDIT: By the way we have a new video.
http://fusioncast.blogspot.com/

Jupiter

[rhomp2002]

I just tried to do a pretend update deep world and it failed because it could not create a depgraph. The problem appears to be masked packages tied to fusion. I am not in the least interested in using fusion at this time at all. If I delete it will this mess up the rest of the latest version of world update? I am thinking that if I just unmerge fusion, then I should be good to go but not sure just how much to unmerge without losing the monitor.

Any suggestions on getting rid of fusion?

Might want to emerge it later but right now it offers me nothing I want.