Package Base Details: rssguard-git

Git Clone URL: (read-only, click to copy)
Submitter: pmattern
Maintainer: pmattern
Last Packager: pmattern
Votes: 5
Popularity: 0.000000
First Submitted: 2016-06-08 17:10 (UTC)
Last Updated: 2022-04-10 13:21 (UTC)

Latest Comments

1 2 Next › Last »

pmattern commented on 2022-04-10 14:12 (UTC)

Cannot reproduce, neither on current master nor after checking out 2a36425b, the current commit when you wrote your comment.
Feel free to report back, if you're still seeing this issue.

This is now - finally! - implemented.
Feel free to test and report back if you're facing problems.

kescherAUR commented on 2021-01-03 02:11 (UTC)

pkgver() returns devbuild.<revisions>.<commithash> (e.g. devbuild.45.g2a36425b-1). The premade pkgver has a numeric version string as prefix. This will tell some AUR helpers to always build the package, even though no changes occurred since the last version.

gbr commented on 2020-11-18 18:57 (UTC) (edited on 2020-11-18 18:58 (UTC) by gbr)

Hi, thanks for updating the package. Can you also split this and make rssguard-nowebengine-git (just like the PKGBUILD in the official repos)? Thanks!

malcolm commented on 2020-05-21 13:17 (UTC)

Thanks @gromain

gromain commented on 2020-04-20 09:39 (UTC)

Hey, build doesn't work since was moved to .

Line 27 of the PKGBUILD should read qmake $srcdir/$_pkgname/ \.

skunkos commented on 2017-10-16 04:38 (UTC)

Starting from 3.5.1, your "make" part of PKGBUILD won't probably work. Use this code snippet instead: qmake ../ -r CONFIG+=release PREFIX=$pkgdir/usr LRELEASE_EXECUTABLE=lrelease-qt5 make

skunkos commented on 2016-08-29 06:33 (UTC)

New version 3.3.4 requires at least Qt 5.6 (previous minimal Qt was 5.7) and can be compiled WITHOUT WebEngine (see file for relevant switch).

pmattern commented on 2016-07-27 12:01 (UTC)

This isn't necessary either. Dependency qt5-webengine will pull qt5-base and both are version 5.7 already. Thus using an inappropriate version can only happen when users install outdated Qt versions on purpose. But these users have to know what they're doing anyway. So I won't add a dependency on a distinct version which represents another albeit minor item that has to be taken care of just to cover this particular case.

skunkos commented on 2016-07-27 07:01 (UTC)

Indeed, anyway, you should update the PKGBUILD, because there is qt5-base dependency which needs to be atleast 5.7, same as webengine.

pmattern commented on 2016-07-22 09:34 (UTC) (edited on 2016-07-22 09:36 (UTC) by pmattern)

@skunkos To my knowledge it's common practice to not update the value of variable pkgver in packages providing latest VCS checkouts when new upstream releases are published and hence no need to flag those packages out-of-date either. The value is updated while building those packages by function pkgver(), see Also, considering the purpose of those packages users will update them regularly and in particular more frequently than official release are published anyway so releases aren't that important.