Package Details: compiz 0.9.14.2-9

Git Clone URL: https://aur.archlinux.org/compiz.git (read-only, click to copy)
Package Base: compiz
Description: Composite manager for Aiglx and Xgl, with plugins and CCSM
Upstream URL: https://launchpad.net/compiz
Licenses: MIT, GPL-2.0-or-later, LGPL-2.1-or-later
Conflicts: ccsm, compiz-bcop, compiz-core, compiz-fusion-plugins-experimental, compiz-fusion-plugins-extra, compiz-fusion-plugins-main, compiz-gtk, compizconfig-python, libcompizconfig, simple-ccsm
Provides: ccsm, compiz-bcop, compiz-core, compiz-plugins-extra, compiz-plugins-main, compizconfig-python, libcompizconfig
Submitter: None
Maintainer: xiota
Last Packager: xiota
Votes: 165
Popularity: 0.009114
First Submitted: 2014-08-04 13:22 (UTC)
Last Updated: 2024-10-31 17:58 (UTC)

Required by (28)

Sources (9)

Latest Comments

« First ‹ Previous 1 .. 32 33 34 35 36 37 38 39 40 41 42 .. 55 Next › Last »

SplitFire commented on 2015-04-15 13:44 (UTC)

Metacity 3.16 landed in stable...

<deleted-account> commented on 2015-04-11 14:54 (UTC)

Notes on the transition to Metacity 3.16: 1) gtk-window-decorator (as it is now) isn't compatible with Metacity 3.16 so expect to have no window borders after the Metacity upgrade. The Metacity maintainer has fixed gwd but his work hasn't been merged upstream yet (and is unlikely to be merged ahead of Metacity 3.16 hitting our repos). The good news is, I've got an updated version of this package with the unmerged Metacity fixes ready to go. I'll upload it to the AUR following the Metacity 3.16 update. 2) If you've been using the Adwaita theme with gtk-window-decorator you may have noticed that, following the GNOME 3.16 upgrade, you're stuck with a weird fallback theme. This is because the Adwaita Metacity theme has been removed from gnome-themes-standard as Mutter won't be using Metacity themes going forward. Instead, it will be using GTK themes. This is no big deal for us. Metacity will continue to use Metacity themes (though it will be compatible with the new paradigm of using GTK themes) and the Adwaita Metacity theme will be shipped with Metacity itself. 3) Metacity themes will no longer defined under org.gnome.desktop.wm.preferences. Instead, they will be defined under org.gnome.metacity. Don't forget to define your Metacity theme under the new schema when Metacity 3.16 hits. Titlebar buttons will still be defined under org.gnome.desktop.wm.preferences. That's all folks.

<deleted-account> commented on 2015-03-19 11:05 (UTC)

Ok I figured out the problem. CMake 3.2 sets an incorrect Python build directory for some reason so the system looks for the Python scripts in the wrong place. I've fixed this simply by using sed to set the correct directory manually. Hopefully Compiz will now build with CMake 3.2 successfully. Let me know if there are issues.

sliposk commented on 2015-03-18 15:26 (UTC)

Thank You Chazza I can confirm the downgrade to cmake 3.1 works.

<deleted-account> commented on 2015-03-18 14:13 (UTC)

@sliposk I was looking at this error just now coincidentally! The problem is with the today's update of CMake. Downgrade to CMake 3.1 and the build will work. I think the issue is something to with character encoding - from the CMake 3.2 release notes: "Files written in the cmake-language(7), such as CMakeLists.txt or *.cmake files, are now expected to be encoded as UTF-8. If files are already ASCII, they will be compatible. If files were in a different encoding, including Latin 1, they will need to be converted."

<deleted-account> commented on 2015-03-18 14:12 (UTC)

@sliposk I was looking at this error just now coincidentally! The problem is with the CMake update to day. Downgrade to CMake 3.1 and the build will work. I think the issue is something to with character encoding - from the CMake 3.2 release notes: "Files written in the cmake-language(7), such as CMakeLists.txt or *.cmake files, are now expected to be encoded as UTF-8. If files are already ASCII, they will be compatible. If files were in a different encoding, including Latin 1, they will need to be converted."

sliposk commented on 2015-03-18 13:56 (UTC)

Here is some more info . compizconfig/ccsm/CMakeFiles/ccsm_module.dir/build.make:64: recipe for target 'compizconfig/ccsm/build/lib.linux-unknown-2.7/ccm/Constants.py' failed make[2]: *** [compizconfig/ccsm/build/lib.linux-unknown-2.7/ccm/Constants.py] Error 1 CMakeFiles/Makefile2:6092: recipe for target 'compizconfig/ccsm/CMakeFiles/ccsm_module.dir/all' failed make[1]: *** [compizconfig/ccsm/CMakeFiles/ccsm_module.dir/all] Error 2 Makefile:146: recipe for target 'all' failed make: *** [all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build compiz.

sliposk commented on 2015-03-18 13:37 (UTC)

Hello, Just went to update to 0.9.12.1-2 and it stopped building with a error. ( mkdir: cannot create directory 'build': File exists ) Looks like this is a new package update as of today 3-18-2015. I will look deeper to see if I can find a fix.

<deleted-account> commented on 2015-03-18 09:58 (UTC)

This is a trivial update to rationalise the Compiz optdeps. I removed the KDE4 stuff as I'm pretty sure the number of people using the KDE window decorator is nil. I've also removed gnome-control-center as that seems to serve no function at all. Finally, I removed gconf - I can't think of a single reason why someone would still want to build Compiz with the GConf Backend. Hope this acceptable for everyone.

<deleted-account> commented on 2015-02-03 13:29 (UTC)

Updated to 0.9.12.1

« First ‹ Previous 1 .. 32 33 34 35 36 37 38 39 40 41 42 .. 55 Next › Last »