Package Details: p4v 2024.3.2649657-1

Git Clone URL: https://aur.archlinux.org/p4v.git (read-only, click to copy)
Package Base: p4v
Description: Perforce Visual Client
Upstream URL: https://www.perforce.com
Keywords: p4 p4merge perforce
Licenses: custom:p4v
Submitter: 1ace
Maintainer: Nephyrin
Last Packager: Nephyrin
Votes: 22
Popularity: 0.000000
First Submitted: 2015-08-12 22:16 (UTC)
Last Updated: 2024-09-12 21:53 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

dront78 commented on 2019-11-19 07:32 (UTC) (edited on 2019-11-19 07:45 (UTC) by dront78)

@jshap the hack is still working.
: > /usr/share/p4v/lib/P4VResources/skins/Default.qss
p4v will use the desktop skin after restart in KDE.
For the non-qt I think you can create a symlink to your skin. PS. dark theme has better color theme in diff util. shame, it is still not possible to setup like in any modern app.
Finally, I ended up with switching to the DarkTheme.css which has a zero file size :)

jshap commented on 2019-10-31 18:23 (UTC) (edited on 2019-10-31 18:23 (UTC) by jshap)

@dront78 I messed around with doing that for the default skin file, but on non-qt based platforms it ends up looking very bad.

Fortunately 19.2 now has a native dark theme (edit->preferences->display->color scheme) though so maybe try that out? Although sadly it doesn't look like we can register custom themes either grumble grumble

guardian commented on 2019-10-30 13:14 (UTC)

Installing fails with p4v-2019.1.1830398.tgz not passing sha256sum test

dront78 commented on 2019-08-16 08:28 (UTC)

could you replace p4v/lib/P4VResources/skins/Default.qss with blank file before the packaging? in this case p4v will looks like a native app even when using kde dark theme.

BorjaOuterelo commented on 2017-12-21 08:06 (UTC)

I found problems with the last P4 released version. Last package version is 2017.3.1601999 and the shas256 for .tgz is no longer valid.

This is the new PCKBUILD file:

https://gist.github.com/BorjaOuterelo/39f0285535c6e25cc482e30a4377a185

Can you update it?

Thanks in advance.

timofonic commented on 2017-11-19 23:32 (UTC)

2017.3/1590419 ftp://ftp.perforce.com/perforce/r17.3/bin.linux26x86_64/SHA256SUMS http://cdist1.perforce.com/perforce/r17.3/bin.linux26x86_64/SHA256SUMS http://cdist2.perforce.com/perforce/r17.3/bin.linux26x86_64/SHA256SUMS http://cdist1.perforce.com/perforce/r17.3/bin.linux26x86_64/p4v.tgz http://cdist2.perforce.com/perforce/r17.3/bin.linux26x86_64/p4v.tgz ftp://ftp.perforce.com/perforce/r17.3/bin.linux26x86_64/p4v.tgz snapshot http://cdist1.perforce.com/perforce/snapshot/p4v/bin.linux26x86_64/SHA256SUMS http://cdist2.perforce.com/perforce/snapshot/p4v/bin.linux26x86_64/SHA256SUMS ftp://ftp.perforce.com/perforce/snapshot/p4v/bin.linux26x86_64/SHA256SUMS http://cdist1.perforce.com/perforce/snapshot/p4v/bin.linux26x86_64/p4v.tgz http://cdist2.perforce.com/perforce/snapshot/p4v/bin.linux26x86_64/p4v.tgz ftp://ftp.perforce.com/perforce/snapshot/p4v/bin.linux26x86_64/p4v.tgz

bwidawsk commented on 2017-10-27 14:57 (UTC)

Please don't flag this out of date for version 1582486. Perforce made a new version without actually updating p4v, so there is nothing to do for p4v.

ainola commented on 2017-10-20 15:46 (UTC) (edited on 2017-10-20 15:48 (UTC) by ainola)

[update] I'm stupid: I thought I had cleared the cache, but I hadn't. It might be useful to save the tarball to a unique filename so helpers don't get confused (e.g. "p4v-$pkgver.tgz"::'sourceurl') It appears that p4v.tgz's checksum is failing. New version? Thanks for maintaining.

BorjaOuterelo commented on 2017-10-04 10:03 (UTC)

P4 updated package. To be updated with package 2017.2.1573260 and new p4c.tgz shas256: f202c09af2df94e89188a15abb763f38a521051febf5f2f0fce72a95062bc228

ainola commented on 2017-09-06 23:52 (UTC)

The .install file is not necessary and can be removed.

« First ‹ Previous 1 2 3 4 5 Next › Last »