Package Details: pcsx2-git 2.3.311.r1.gf45840a29f-1

Git Clone URL: https://aur.archlinux.org/pcsx2-git.git (read-only, click to copy)
Package Base: pcsx2-git
Description: PlayStation 2 emulator
Upstream URL: https://github.com/PCSX2/pcsx2
Licenses: GPL-3.0-or-later
Conflicts: pcsx2
Provides: pcsx2
Submitter: alucryd
Maintainer: weirdbeard (xiota)
Last Packager: weirdbeard
Votes: 133
Popularity: 1.85
First Submitted: 2014-03-26 14:17 (UTC)
Last Updated: 2025-05-04 04:17 (UTC)

Pinned Comments

weirdbeard commented on 2024-08-17 03:40 (UTC)

https://github.com/PCSX2/pcsx2/pull/11632

This package now enables Cmake Package mode proper. PCSX2 will here on, be installed in the package standard folders /usr/bin, /usr/share, /usr/lib. Following the XDG standard pcsx2's config files remain in .config/PCSX2

In order to ensure a proper and clean upgrade. Uninstall this package COMPLETELY and clear cache before reinstalling.

Latest Comments

1 2 3 4 5 6 .. 72 Next › Last »

AirGamer commented on 2025-05-04 10:45 (UTC)

@xiota you stated in an earlier comment that plutosvg and pcsx2 demanded versions that where impossible to satisfy, and then denied that this was due to your packaging patches, those are both lies.

plutosvg will configure and build unmodified with plutovg 0.0.13 because CMake treats it as a compatible version, infact if you check the git at tag/v0.0.6 (https://github.com/sammycage/plutosvg/tree/v0.0.6) they use 0.0.12 as a submodule, not the version CMake requested but instead a compatible version. no conflicting version requirements here.

Both plutosvg v0.0.6 and pcsx2 (when pluto was added) would have rejected 1.0.0, no conflict here either.

Patching plutosvg allowed the conflict around plutovg 1.0.0 you complained about, not pcsx2.

Yes plutovg 1.0.0 turned out to be source compatible, which means CMake unnecessarily rejected it (which is arguably more a fault of plutovg's version file then the dependent projects). But, as much as it is annoying, to claim it impossible to satisfy is outright wrong.

AirGamer commented on 2025-05-04 02:53 (UTC) (edited on 2025-05-04 03:03 (UTC) by AirGamer)

The only misleading information was implying that pcsx2 was the cause of package conflict, when infact the conflict could only have occured thanks to the aur patch applied to plutosvg.

I don't necessarily have an issue with you patching things to get a later version of plutovg working, but to claim that pcsx2 is the cause of the conflict instead of your patches is an outright lie, and was what I an had issue with.

weirdbeard commented on 2025-05-04 02:24 (UTC)

I don't mind making whatever changes Air wants.

AirGamer commented on 2025-05-04 02:00 (UTC)

@xiota Looking at the aur PKGBUILD for plutosvg, it is using CMake to build, and uses sed to modify the CMakefile to accept the newer plutovg version, I don't see why the loser requirements of meson are relevant when it isn't being used to build.

AirGamer commented on 2025-05-03 20:09 (UTC)

Version requirements for plutovg are impossible to satisfy because plutosvg and pcsx2 demand different versions, so they have to be adjusted.

For the record, you are patching plutosvg to build with plutovg v1.0.0. The CMake file for the latest release of plutosvg (v0.0.6 at the time) asked for an older plutovg version (v0.0.4 with v0.0.13 being the latest accepted), which is why pcsx2 asked for the version it did. A later commit to plugosvg has bumped the version of plutovg needed, but no release carrying that change has been made yet.

To accommodate this, pcsx2's version requirement for plutovg has been dropped, as it should use the same version used for plutosvg.

weirdbeard commented on 2025-05-01 11:36 (UTC)

Right on. Thanks for catching that one

1 2 3 4 5 6 .. 72 Next › Last »