Package Details: compiz-manjaro 0.9.13.0-5

Git Clone URL: https://aur.archlinux.org/compiz-manjaro.git (read-only)
Package Base: compiz-manjaro
Description: OpenGL compositing window manager. Includes friendly defaults, GWD theme selector and autostart for Xfce & MATE.
Upstream URL: https://launchpad.net/compiz
Licenses: GPL, LGPL, MIT
Conflicts: ccsm, compiz, compiz-bcop, compiz-core, compiz-core-bzr, compiz-core-devel, compiz-core-mate, compiz-decorator-gtk, compiz-decorator-kde, compiz-fusion-plugins-experimental, compiz-fusion-plugins-extra, compiz-fusion-plugins-main, compiz-fusion-plugins-unsupported, compiz-gtk-standalone, compiz-mate, compiz-xfce, compiz09-manjaro-test, compizconfig-backend-gconf, compizconfig-python, libcompizconfig
Provides: compiz=0.9.13.0
Replaces: compiz09-manjaro-test
Submitter: korrode
Maintainer: korrode
Last Packager: korrode
Votes: 24
Popularity: 0.387704
First Submitted: 2014-07-27 15:36
Last Updated: 2016-10-19 23:17

Latest Comments

annoyingduck commented on 2017-02-12 17:42

@Chazza, I misunderstood the replacement dependency. I didn't remove the compizcconfig-python, only the compiz-core. Thanks, got it to work.

Chazza commented on 2017-02-12 10:36

@annoyingduck I'm not quite sure what you're doing here. You shouldn't be building compizconfig-python or libcompizconfig or any other Compiz 0.8 packages for that matter.

The various Compiz components were once developed and packaged separately. This is why you had a package for compiz-core, for ccsm, for libcompizconfig etc etc. But with Compiz 0.9.8, the components were all rolled into one package called Compiz. As such, this package (compiz-manjaro) already provides compizconfig-python and it already provides libcompizconfig and it already provides compiz-core. Have a look at the provides and conflicts lines on the compiz package to get an idea: https://aur.archlinux.org/packages/compiz/

So to install emerald or fusion-icon you do not need to build or install ANY of the Compiz 0.8 packages. You only need compiz-manjaro and you only need to edit the fusion-icon/emerald pkgbuilds to replace the dependency on compizcconfig-python/compiz-core with one on compiz-manjaro. And you only need to do that because the compiz-manjaro pkgbuild doesn't claim to provide compiz-core or compizconfig-python.

You know, you can make a pkgbuild claim to provide anything you like and it doesn't matter in the slightest, just as long as you know what you're doing. :D

As an aside, the build error you were getting was because you were trying to build the Compiz 0.8 version of libcompizconfig against the Compiz 0.9 version of compiz-core which is provided by compiz-manjaro. That simply won't work as the two codebases are entirely different.

You also can't do something like "I/usr/include/compiz-manjaro \". The name compiz-manjaro is nothing more than a name in pacman's database. The software itself is still called compiz and the header files will still be in /usr/include/compiz.

annoyingduck commented on 2017-02-12 00:22

@Chazza I still cannot get fusion-icon to build. I was able to get compizconfig-python to build, but I'm stuck on libcompizconfig. I removed the compiz-core dependency and added compiz-manjaro, but I'm still getting a fatal error: compiz-core.h: No such file or directory. I then changed in the CPPFLAGS I/usr/include/compiz-manjaro \ (over compiz-core). Something in the script is still looking for compiz-core and I don't know what else it could be.

Chazza commented on 2017-02-11 16:15

@annoyingduck Ah yes, that's a dependency issue. The compiz-manjaro pkgbuild needs to provide compizconfig-python to satisfy fusion-icon and it needs to provide compiz-core to satisfy emerald. I did this a while back for compiz: https://aur.archlinux.org/cgit/aur.git/commit/?h=compiz&id=f346f6005663969c430d873b1aae37a8ab1ab150

In the meantime, the easiest thing to do would be to edit the fusion-icon pkgbuild and replace the dependency on compizconfig-python with a dependency on compiz-manjaro. Likewise, if you want emerald then replace the dependency on compiz-core with a dependency on compiz-manjaro.

Hope this helps!

annoyingduck commented on 2017-02-11 16:00

@Chazza I could not get fusion-icon to build with compiz-manjaro. I tried pamac, yoaurt -S, yoaurt -Sa, dependency conflict (I'm guessing compiz-manjaro vs compiz). Any suggestions?

PhotonX commented on 2017-02-11 12:27

Please add default options fixing this bug: https://bugs.manjaro.org/index.php?do=details&task_id=121&status%5B0%5D=open&order=id&sort=desc (see comments to the bug)

Chazza commented on 2017-02-11 11:47

fusion-icon0.9 and emerald0.9 shouldn't exist anymore. I had them removed from the AUR last year. The latest versions of emerald and fusion-icon in the AUR work with Compiz 0.9. Use those instead.

annoyingduck commented on 2017-02-10 17:45

Love that this is in the AUR. Will this be updated to the latest version, and anyway to get fusion-icon working? Or maybe adding Manjaro's fusion-icon.09 as another build?

rafaelgomes commented on 2016-10-14 20:30

After the metacity (3.22) update, the window decorator stop working.

gtk-window-decorator: error while loading shared libraries: libmetacity.so.0: cannot open shared object file: No such file or directory

Chazza commented on 2016-08-18 11:22

Thanks for your opinion on it. I think what bothers me most is not those two particular settings but the fact that it touches settings for lots of different plugins which may not affect me personally but may bother other users. I think I'm going to stick with reverting r3981 for now and then review the situation on the next point release.

All comments