Package Details: compfy 1.7.2-1

Git Clone URL: https://aur.archlinux.org/compfy.git (read-only, click to copy)
Package Base: compfy
Description: A Linux Compositor for X11. Based on Picom. Providing Animations and More
Upstream URL: https://github.com/allusive-dev/compfy
Licenses: MIT, MPL2
Submitter: None
Maintainer: Levitating
Last Packager: None
Votes: 5
Popularity: 1.10
First Submitted: 2023-11-15 04:41 (UTC)
Last Updated: 2023-12-01 22:00 (UTC)

Latest Comments

MarsSeed commented on 2023-12-10 10:18 (UTC) (edited on 2023-12-10 10:19 (UTC) by MarsSeed)

This needs the following depends as per namcap analysis and Arch package guidelines:

Thank you for maintaining it!

<deleted-account> commented on 2023-11-25 22:02 (UTC)

Ah alright I understand. I'll make the changes soon!

Erus_Iluvatar commented on 2023-11-25 06:42 (UTC)

Sorry for the late reply: if both packages can be installed at the same time (i.e. picom is not deprecated and replaced by compfy, nor does compfy ship a compton symlink) but simply provide conflicting functions, it's not something we handle in a PKGBUILD: e.g. sddm and gdm can't run at the same time but their packages don't conflict with each other. It's up to the user to adjust their setup accordingly, so removing the conflicts and provides arrays is enough.

<deleted-account> commented on 2023-11-17 10:35 (UTC)

So I should just completely remove the conflicts and provides? I'm questioning it because compfy should fill the place of picom and also conflict with it.

Erus_Iluvatar commented on 2023-11-17 10:33 (UTC)

Thanks a bunch :) For the conflicts/provides, simply not having the lines in the PKGBUILD should be enough?

<deleted-account> commented on 2023-11-16 09:26 (UTC)

Good News, I fixed the issue of installing to "/usr/local" thanks to your suggestion of "--prefix=/usr"

I also changed it as you suggested by adding a pkgver function and cloning via the release tag.

<deleted-account> commented on 2023-11-16 08:37 (UTC)

Hello Erus, I have had a go at fixing some of the things you mentioned. I am not sure how to fix the second and third issues you raised even after doing a fair bit of research. In terms of fixing the binary installation location I will push an update to the program that should fix it soon.

Erus_Iluvatar commented on 2023-11-16 08:00 (UTC)

Hi,

Could you please update your PKGBUILD to follow https://wiki.archlinux.org/title/Arch_package_guidelines#Package_etiquette ?

A few things that jumped to my eyes is the PKGBUILD :

  • installs its binaries to /usr/local (probably missing something like "--prefix=/usr" or "--buildtype=release" as an argument to the meson setup?),
  • uses a provides and conflicts array but does not actually provide any conflicting binary with these packages: they can still be installed side-by-side even if they can't run at the same time for the same user session (same as conflicting network managers, for example),
  • the source should be updated to use an object hash as explained in https://wiki.archlinux.org/title/Arch_package_guidelines#Package_sources or simply use the release tarball?
  • creates the $_gitfolder and $_gitname variables instead of simply using $pkgname.