-> Cloning ppsspp-ffmpeg git repo...
Cloning into bare repository '/tmp/yaourt-tmp-skeith/aur-ppsspp-qt-git/ppsspp-ffmpeg'...
remote: Counting objects: 8920, done.
remote: Compressing objects: 100% (5441/5441), done.
Receiving objects: 71% (6363/8920), 276.82 MiB | 84.00 KiB/s
That's rather big for just FFMPEG
Search Criteria
Package Details: ppsspp-assets-git 1.17.1.r785.cbdb2a37eb-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/ppsspp-git.git (read-only, click to copy) |
---|---|
Package Base: | ppsspp-git |
Description: | A PSP emulator written in C++ |
Upstream URL: | https://www.ppsspp.org/ |
Licenses: | GPL2 |
Conflicts: | ppsspp-assets |
Provides: | ppsspp-assets |
Submitter: | libcg |
Maintainer: | loathingkernel |
Last Packager: | loathingkernel |
Votes: | 43 |
Popularity: | 0.31 |
First Submitted: | 2012-11-05 20:36 (UTC) |
Last Updated: | 2024-06-21 11:26 (UTC) |
Dependencies (14)
- clang (llvm-rocm-gitAUR, llvm-gitAUR, clang-minimal-gitAUR) (make)
- cmake (cmake-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- glew (glew-libepoxyAUR, glew-waylandAUR, glew-osmesa-gitAUR, glew-wayland-gitAUR, glew-gitAUR) (make)
- glu (glu-gitAUR) (make)
- libglvnd (libglvnd-gitAUR) (make)
- libpng (libpng-gitAUR, libpng-apngAUR) (make)
- libzip (libzip-gitAUR) (make)
- ninja (ninja-kitwareAUR, ninja-memAUR, ninja-fuchsia-gitAUR, ninja-gitAUR, ninja-jobserverAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- sdl2 (sdl2-gitAUR, sdl2-compat-gitAUR) (make)
- sdl2_ttf (make)
- snappy (snappy-gitAUR) (make)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compat) (make)
Required by (2)
- libretro-ppsspp-git (requires ppsspp-assets) (optional)
- ppsspp-git
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 Next › Last »
jkcdarunday commented on 2014-05-14 12:20 (UTC)
m45t3r commented on 2014-03-25 23:42 (UTC)
New version v0.9.8.r132.g1d21306-1:
-Fix pkgver to use a valid PPSSPP git version. This fix AUR helpers so they don't always list this package as available to update.
misc commented on 2014-03-08 17:19 (UTC)
It doesn't actually break the helpers, rather it makes them believe that you updated this PKGBUILD, and thus permanently list it as available update, which quickly becomes quite annoying. I have to edit it out manually every single time.
All it would take is to update the pkgver=20131128 line. If you take a look at the "Recent Updates" box on AUR's main page, you'll also notice that next to no packager uses the date anymore.
<deleted-account> commented on 2014-02-24 15:15 (UTC)
Package seems to building fine without needing any modifications to build().
Apart from that, I removed ffmpeg dependency as the project uses its own ffmpeg, and I added a pkgver() function.
libcg commented on 2014-02-19 19:04 (UTC)
I disowned the two packages, not much time to take care of it as you may have noticed.
m45t3r commented on 2014-02-18 22:05 (UTC)
pkgver should be updated automatically (with the pkgver() function), so I used the data of the lastest time I made modifications.
Still, I am aware this break AUR helpers since they think this PKGBUILD is newer than the installed one. I don't know if it's better to change the pkgver to just after a build or not.
Anyway, this package seems pretty stable too: almost two months with no modifications. I don't want to update it just to change the pkgver.
misc commented on 2014-02-12 13:15 (UTC)
pkgver must be updated (eg to v0.9.6.r900.gcaf729e).
m45t3r commented on 2013-12-25 16:04 (UTC)
I am using a modified .desktop file from upstream, so if you think you can improve the .desktop file I think you should report to upstream.
After they fix it I can change the package too.
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.