@kage52124 The idea is that keeping them together in a PKGBUILD makes them stay at same version naturally. The subpackage ppsspp-common-git is needed by all variants and ideally needs to be from the same source version as those variants. Keeping them in a single PKGBUILD prevents version mismatch. I think it would not be reliable if we seperate them into individual PKGBUILDs and have dependencies with version locked as there is no way to be sure that the sources downloaded would be at exactly the same version when building them seperately.
You can always edit PKGBUILD before building to prevent builds that you don't need. If you need prebuilt packages, I also provide them at https://aurbuild.xdavidwu.link/ (daily builds) signed with key F73F137D4573DEFAA097DBF09544CFF6B08A3FD3.
Pinned Comments
xdavidwu commented on 2021-02-09 03:30 (UTC)
Please don't flag this package out-of-date when you see the version string is. This is a VCS package. It always grabs the latest source from upstream repo and version string is generated at build time. As long as it builds fine, it is up-to-date. It is your responsibility to decide when to rebuild (update). I won't bump the version for you.
Also, I am running a daily build service, and by that, I can check that it builds fine daily. Ancient version string does not mean that I have loose track of the latest source.