Package Details: picom-git 2530_11.513.g7094d7a9_2024.07.31-1

Git Clone URL: https://aur.archlinux.org/picom-git.git (read-only, click to copy)
Package Base: picom-git
Description: X compositor (fork of compton) (git-version)
Upstream URL: https://github.com/yshui/picom
Licenses: MIT, MPL-2.0
Conflicts: compton, compton-git, picom
Provides: compton, compton-git, picom
Replaces: compton-git
Submitter: WorMzy
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 359
Popularity: 0.51
First Submitted: 2019-10-24 11:20 (UTC)
Last Updated: 2024-07-31 09:54 (UTC)

Required by (21)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 Next › Last »

Dea993 commented on 2014-01-25 09:00 (UTC)

is better compton or compton-git version?

<deleted-account> commented on 2014-01-17 19:27 (UTC)

Works real nice with openbox. Thanks :)

mrkline commented on 2013-12-23 23:59 (UTC)

@jyc: I did it by mistake. My apologies.

jyc commented on 2013-11-14 05:18 (UTC)

Why is this flagged as out of date?

OK100 commented on 2013-10-24 07:49 (UTC)

@intelfx: I also prefer the current pkgver

<deleted-account> commented on 2013-10-21 14:35 (UTC)

I prefer the current versionning with the date…

intelfx commented on 2013-10-21 13:52 (UTC)

Could you please update PKGBUILD to use epoch=1 instead of date in pkgver()? It's less cluttered... Package with an example pkgver is here: ftp://intelfx.dyndns.org/compton-git-1:0.1.beta1.17.g796e2c6-1.src.tar.gz

msx commented on 2013-10-15 09:25 (UTC)

Awesome, thanks for packaging guys!

brettski commented on 2013-08-08 14:52 (UTC)

@WorMzy: that seems valid. Rebuilding did fix the problem. My thinking was that people using an AUR helper would do not see that the application has been updated to fix a major bug. It seemed to me that updating the PKGBUILD (even if just the name) to reflect the most recent commits would help with that problem. I am still learning about the Arch Way and AUR etiquette. In an unrelated issue, when trying to rebuild this package with aura it insisted that I needed mesa-libgl... of course that conflicted with nvidia-libgl and I was not able to proceed. Installing the tarball manually worked without any trouble. Any idea what that might be about?

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 Next › Last »