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.009300
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 .. 10 11 12 13 14 15 16 17 18 19 20 .. 55 Next › Last »

denjack commented on 2019-03-28 17:00 (UTC)

Hello Chazza, thank you for providing this package. Please why there is missing KDE Compatibility plugin in the package? I can see Gnome Compatibility and MATE Compatibility in CCSM but not KDE. KDE Compatibility is needed to have window thumbnails in DockBarX which is the most important, if not the only reason why i'm delaing with compiz. Noticed this plugin is available in Linux Mint compiz package version 0.9.13 i looked for it, but there is absolutely no information about it over the internet. Just as an attempt i tried to change -DBUILD_KDE from Off to On in PKGBUILD of your package and recompile it but no change, even no KDE decorator (the meaning for this configure option as far as i know) have appeared then. Do i something wrong or is the KDE Compatibility really missing in your package and if so why or how it can be add there? Thank you

xebuzer0 commented on 2019-03-25 06:14 (UTC)

@Chazza: Even I'm going to read those wiki pages to see other interesting thinks realated. Now I have a new knowledge that is makepkg with "si" argument, and like some other users, after "rebuilding" Compiz now works as good as always. Thanks a lot!

<deleted-account> commented on 2019-03-24 09:14 (UTC)

Hello xebuzer0

Documentation for the AUR can be found here: https://wiki.archlinux.org/index.php/Arch_User_Repository

I suggest you have a good read through. In fact, all documentation relating to Arch Linux can be found on wiki.archlinux.org. Just search it for your topic of choice.

To very briefly summarise the building part though, the way you build a package is you download the source package (either by going to the package webpage and clicking "Download snapshot" and then extracting the contents of the tarball or by running git clone <https://aur.archlinux.org/compiz.git>). Then you open a terminal inside the directory containing the source package contents and run makepkg -si. The -s option prompts you to install missing dependencies and the -i option prompts you to install the built package. To rebuild, you simply run makepkg again. You first need to remove the .pkg.tar.xz package created last time (assuming the build succeeded) and you might also need to remove the src directory as well if patch is complaining that there are patches that have already been applied.

As for symlinking new library names to old, please, please don't do this. It is NEVER a good solution. Shared library versions don't change for no reason. They change because the new library is not completely completely compatible with the old. If the program linked against the shared library depends on functionality that changed between the old and new versions of the library then you will run into strange problems and nobody will know what's going on. Also, you will get into a mess because you will lose track of which symlinks were created by you and which ones were created by the package manager.

xebuzer0 commented on 2019-03-24 08:16 (UTC)

@Chazza I just have a little problem... there's some documentation about what exactly means and how to "rebuild the package"? I've also tried uninstalling, cleaning cache and reinstalling but I get the same error, and even the sim-link doesn't helps because I get exactly the same error and the same "undefined symbol" string of @GaylairdCulbreth.

Thanks in advance and I hope you can help me, I'm a little newbie in the Arch World.

<deleted-account> commented on 2019-03-18 23:09 (UTC)

@Sebversive If you run an executable linked against shared libaries in the terminal, and any of those links are broken (i.e. /usr/bin/compiz is linked against libfoo.so.5 but libfoo got updated to libfoo.so.6) then you will get a message in the terminal saying something along the lines of:

shared object libfoo.so.5 could not be found.

And at that point you know you need to rebuild the package that provides that executable (in this case compiz). So this problem only occurs if the version number of a shared object file changes.

Some AUR maintainers will bump the pkgrel of their AUR packages every time there's a shared library that gets its version updated and then people that use AUR helpers like yaourt will have a rebuild triggered when they run their helper. I'm afraid I don't do this for compiz though, mainly because I don't use compiz any more so I don't know when the shared library versions change. I only build compiz and run it when there's an update or when there are issues reported here. I have previously stated - and will state again - that if anyone is unhappy with this, I am more than happy to hand over maintenance of compiz to someone else. Just send me an email.

With all that being said about AUR helpers, I would advise staying away from them anyhow, at least until you're completely familiar with how the AUR and building packages work.

Hope this helps

<deleted-account> commented on 2019-03-18 02:20 (UTC)

@Chazza; are you telling me I'm supposed to keep an eye on every single dependency my AUR packages have and notice myself if an AUR package needs rebuilding??

<deleted-account> commented on 2019-03-15 19:17 (UTC)

@Sebversive compiz builds fine here. No idea why your build failed on at 34%. And yes, compiz (and all AUR packages in general) need to be rebuilt when dependencies that they're linked against get updated.

<deleted-account> commented on 2019-03-15 18:18 (UTC)

Updated my system (last time was 10 days ago) and compiz is broken, doesn't run anymore. Now I tried to reinstall compiz and I get this:

[ 34%] Building CXX object plugins/expo/CMakeFiles/expo.dir/src/expo.cpp.o make[2]: No rule to make target '../plugins/expo/src/glow.cpp', needed by 'plugins/expo/CMakeFiles/expo.dir/src/glow.cpp.o'. Stop. make[1]: [CMakeFiles/Makefile2:9756: plugins/expo/CMakeFiles/expo.dir/all] Error 2 make: *** [Makefile:163: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

Any idea?

Edit: replaced compiz with compiz-git -> everything back to normal..

<deleted-account> commented on 2019-02-20 14:43 (UTC)

@ector, once I'm in front of my Arch machine I'll update this package to add the fix from upstream.

Edit: done.