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.52
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 2 3 4 5 6 7 8 9 10 .. 15 Next › Last »

yshui commented on 2018-10-15 17:49 (UTC)

Cool. I guess I try just stop annotating the vNext tag. That should prevent it from showing up in git describe

WorMzy commented on 2018-10-15 12:21 (UTC)

Haha, don't worry about it. It's unusual for a project to use tags like this, but it's not unheard of. I've changed the way that the pkgver is generated, so it should increment as expected, regardless of whether the latest tag is.

yshui commented on 2018-10-15 11:43 (UTC)

Looking at the changelogs of the PKGBUILD, I noticed that my use of the vNext tag might have caused some trouble for the package maintainer.

My intention is to always use the vNext tag to track the latest commit, so I can use the github release system to keep track of the important changes I made. Besides that, there will also going to be version based tags (e.g. v3).

Now, that seems to create some difficulty in the pkgver handling. So I want to ask what is the packager's opinion on this. Is it fine if I keep using the vNext tag?

WorMzy commented on 2018-10-04 17:25 (UTC)

namcap is only an aide to packagers, some of it's warnings are fine to ignore. In this case, I feel it makes more sense to have the licence installed to a directory named after the project it is a license for, rather than the name of the package.

bidulock commented on 2018-10-04 17:07 (UTC)

You should install license file under /usr/share/licenses/${pkgname}, otherwise, namcap cannot find it.

WorMzy commented on 2018-10-04 12:57 (UTC)

Thanks for the heads up. If yshui has switched the default branch to next, then I feel that is the branch this package should be building from. It may be a bit more buggy, but if you want stability, then you should probably use community/compton anyway.

I'll try to get an updated PKGBUILD pushed out in the next few hours.

bidulock commented on 2018-10-04 11:48 (UTC)

Not really. I think you need #branch=master on the end of source=() now, because the new default branch is 'next'. Otherwise to build on the 'next' branch you will need 'libev' 'xcb-util-image' 'xcb-util-renderutil' and 'pixman' in depends=() and will have to no longer copy the LICENSE file in package=() (as it is no longer there).

Anthony25 commented on 2018-10-03 16:25 (UTC)

Hi, compton now needs libev to build.

ekce commented on 2018-05-21 08:50 (UTC)

Compton currently has a bug where video players will temporarily freeze while the audio continues playing.

I'm pretty sure this has been reported on the github more than once but here is the latest open issue on the bug: https://github.com/chjj/compton/issues/494

Moreover, compton is currently unmaintained so unless someone fixes it in a fork the issue is unlikely to be addressed. For now the only known fix seems to be to stop Compton while playing videos.

WorMzy commented on 2017-11-28 13:40 (UTC)

Ah, I thought you were getting a build failure due to the new libconfig. Yes, you will need to rebuild the package against the new library. Installing avkonarev's package is not a solution, it is a workaround.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 15 Next › Last »