Package Details: pcsx2-git 2.3.35.r0.g4eae1b7127-1

Git Clone URL: https://aur.archlinux.org/pcsx2-git.git (read-only, click to copy)
Package Base: pcsx2-git
Description: A Sony PlayStation 2 emulator
Upstream URL: https://github.com/PCSX2/pcsx2
Licenses: GPL-3.0+
Conflicts: pcsx2
Provides: pcsx2
Submitter: alucryd
Maintainer: weirdbeard (xiota)
Last Packager: weirdbeard
Votes: 130
Popularity: 0.132736
First Submitted: 2014-03-26 14:17 (UTC)
Last Updated: 2024-11-27 22:52 (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

« First ‹ Previous 1 .. 43 44 45 46 47 48 49 50 51 52 53 .. 67 Next › Last »

alucryd commented on 2014-07-29 23:52 (UTC)

Good stuff! I've uploaded lib32-wxgtk, but pcsx2 fails to build when I want to use it, I'll wait until this is solved to up the new PKGBUILD. I've opened an issue about it: https://github.com/PCSX2/pcsx2/issues/172 BTW, I like where this is heading: https://github.com/PCSX2/pcsx2/commit/35979bb5a6bd54ff5335ca00de881e597afaef23

rafaelff commented on 2014-07-29 20:33 (UTC)

.... and the use of sparsehash removed [1] [1] https://github.com/PCSX2/pcsx2/pull/157

rafaelff commented on 2014-07-29 20:31 (UTC)

Hey, just to let you know that support for wxgtk3 was implemented and merged today [1]. [1] https://github.com/PCSX2/pcsx2/pull/156

alucryd commented on 2014-07-28 23:14 (UTC)

Well actually they do use git tags, they tagged 1.2.1 (not 1.2.2 for some reason); the problmen comes from the fact that they bump their version numbers before actually releasing something. Git tags work like this: you tag a release, and subsequent "git describe" will output the latest tag, the number of commits since then and the latest commit hash. In the end, this is probably a matter of preference, lots of programs bump their version numbers right after a release, but imho it makes more sense to not do so when using git. tl;dr They would need to change their versioning, ie stop bumping it after a release, and apart for "it's better to do this with git", there isn't much of an argument here.

rafaelff commented on 2014-07-28 23:01 (UTC)

It would be really nice with they used. I'd would report it to them [1], but I don't have much arguments (I just know just some basics of Git) so I might not be convincing enough. [1] https://github.com/PCSX2/pcsx2/issues

alucryd commented on 2014-07-28 22:44 (UTC)

Sorry about the delay, this had escaped my mind. It's a shame they don't use git tags properly like dolphin's team or pretty much everyone else do because they're very informative, but oh well, ugly pkgver() it is. Thx for pointing it out.

rafaelff commented on 2014-07-22 11:06 (UTC)

Actually my idea is not to repleace the whole version scheme, and my idea is to keep compatible with vercomp and alwasys above stable release. Since git-tags doesn't seem to be much reliable, my idea was to get version from the one piece of code that tells the emulator what is its version. What I mean is, even if you set 1.2.2..etc as the package version, PCSX2 will get 1.3.0 from pcsx2/SysForwardDefs.h and the GUI will be labeled as "PCSX2 1.3.0-(otherstuff)". Talking about codes, my idea was to replace: printf "1.2.2.r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)" ...With something like: major=`grep -o "VersionHi.*" pcsx2/SysForwardDefs.h | grep -o "[0-9]*"` mid=`grep -o "VersionMid.*" pcsx2/SysForwardDefs.h | grep -o "[0-9]*"` minor=`grep -o "VersionLo.*" pcsx2/SysForwardDefs.h | grep -o "[0-9]*"` version="$major.$mid.$minor" printf "$version.r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)" This would result in e.g.: 1.3.0.r5131.70d1719-1

alucryd commented on 2014-07-22 09:53 (UTC)

What do you mean by getting out-of-date? Almost every git package goes like this: 'latest_release_number'.r'number_of_commits_since_latest_release'.'latest_commit_hash'; that scheme is compatible with vercomp and pkgver is always above the stable release. Unfortunately 1.2.2 wasn't tagged, hence the currently weird pkgver, but once 1.3.0 is I'll go back to using 'git describe --tags'. I'm not sure it's useful to have 1.3.0 right now, especially since the pkgver will be above the one I'll get when 1.3.0 is tagged, and I don't want to introduce an ugly epoch.

rafaelff commented on 2014-07-22 01:34 (UTC)

Development version of PCSX2 is currently in version 1.3.0, as can be seen in SysForwardDefs.h[1]. To avoid getting out-of-date, I suggest preparing pkgver's content using the values from this file, like the developer Gregory did in the script "create_pcsx2_tarball_from_svn_repository.sh"[2] (which get from git, btw). Anyway, can you please update the pkgver from 1.2.2 to 1.3.0 ? [1] https://github.com/PCSX2/pcsx2/blob/master/pcsx2/SysForwardDefs.h [2] https://github.com/PCSX2/pcsx2/blob/master/debian-unstable-upstream/create_pcsx2_tarball_from_svn_repository.sh

« First ‹ Previous 1 .. 43 44 45 46 47 48 49 50 51 52 53 .. 67 Next › Last »