Package Details: qt5-styleplugins-git r36-1

Git Clone URL: https://aur.archlinux.org/qt5-styleplugins-git.git (read-only)
Package Base: qt5-styleplugins-git
Description: Additional style plugins for Qt5
Upstream URL: https://code.qt.io/cgit/qt/qtstyleplugins
Licenses: LGPL
Conflicts: qt5-styleplugins
Provides: qt5-styleplugins
Submitter: xduugu
Maintainer: nfnty
Last Packager: nfnty
Votes: 9
Popularity: 0.206365
First Submitted: 2016-06-25 09:41
Last Updated: 2017-07-17 14:26

Required by (4)

Sources (1)

Pinned Comments

nfnty commented on 2016-06-25 11:13

Issues and pull requests at https://github.com/nfnty/pkgbuilds

Latest Comments

1 2 Next › Last »

nfnty commented on 2017-01-24 08:23

@parkerlreed Yeah... That issue has been fixed for a long time now. Check the wiki for more info.

parkerlreed commented on 2017-01-24 08:21

Ok so using

QT_QPA_PLATFORMTHEME=gtk2

Instead of

QT_STYLE_OVERRIDE=gtk2

Makes it work. segfaults with the OVERRIDE option.

nfnty commented on 2017-01-24 08:20

@parkerlreed Have you tried `qt5-styleplugins`?

parkerlreed commented on 2017-01-24 08:18

Anybody else have segfault issues with this? Usually updating the package (and thus recompiling) is enough but it's starting to do it on every Qt application I try.

nfnty commented on 2016-12-21 00:13

@manuelschneid3r No, this is a git package, either you stay updated yourself or start using a non-git package.

manuelschneid3r commented on 2016-12-20 12:35

Since the qt libs are now on 5.7.1 this package has to be recompiled against 5.7.1. Please increment the pkgrel to make sure people rebuild it.

nfnty commented on 2016-10-29 20:55

@raqua: Updated and fixed.

raqua commented on 2016-10-29 20:03

Won't build for me:

==> qt5-styleplugins-git dependencies:
- qt5-base (already installed)
- gtk2 (already installed)
- libx11 (already installed)
- git (already installed) [makedepend]

==> qt5-styleplugins-git conflicts:
- qt5-styleplugins-5.0.0-2

==> Continue building qt5-styleplugins-git ? [Y/n]
==> ----------------------------------------------
==>

==> Building and installing package
==> WARNING: Cannot find the sudo binary. Will use su to acquire root privileges.
==> Making package: qt5-styleplugins-git r22-1 (Sat Oct 29 22:02:32 CEST 2016)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Updating qtstyleplugins git repo...
Fetching origin
-> Found gconf.patch
==> Validating source files with sha512sums...
qtstyleplugins ... Skipped
gconf.patch ... Skipped
==> Extracting sources...
-> Creating working copy of qtstyleplugins git repo...
Switched to a new branch 'makepkg'
==> Starting prepare()...
error: patch failed: src/plugins/styles/styles.pro:5
error: src/plugins/styles/styles.pro: patch does not apply
==> ERROR: A failure occurred in prepare().
Aborting...
==> ERROR: Makepkg was unable to build qt5-styleplugins-git.
==> Restart building qt5-styleplugins-git ? [y/N]
==> ---------------------------------------------
==> n

xduugu commented on 2016-06-26 10:31

> Every application handles versioning differently. It is just not worth the extra effort. If there ever is a problem where a package needs a specific version then that can easily be fixed. No need to use pkgver for that. Arch is rolling release and you only use git packages if you know what you're doing.

It's no extra effort, since there are already well established pkgver defaults. No need for custom version schemes.

https://git.archlinux.org/pacman.git/tree/proto/PKGBUILD-vcs.proto

You just have to distinguish between git repositories with tags and without. Ignoring tags has the big disadvantage that you cannot tell just from the version string, if the build package is newer or older than a specific tag. You always have to look at the repository history.

nfnty commented on 2016-06-26 08:06

I'll just change srcname to something else if it ever becomes a problem.

Every application handles versioning differently. It is just not worth the extra effort. If there ever is a problem where a package needs a specific version then that can easily be fixed. No need to use pkgver for that. Arch is rolling release and you only use git packages if you know what you're doing.