Package Details: plasma5-applets-active-window-control-git 1:r22.8e9fb90-1

Git Clone URL: (read-only, click to copy)
Package Base: plasma5-applets-active-window-control-git
Description: Plasmoid for Plasma 5. Allowes advanced control of active window.
Upstream URL:
Licenses: GPL
Conflicts: plasma-applet-active-window-control-git, plasma5-applets-active-window-control
Provides: plasma5-applets-active-window-control
Submitter: clearmartin
Maintainer: clearmartin
Last Packager: clearmartin
Votes: 25
Popularity: 0.000001
First Submitted: 2015-06-15 17:46 (UTC)
Last Updated: 2018-02-11 00:34 (UTC)

Latest Comments

clearmartin commented on 2018-01-16 23:16 (UTC)

I have updated the epoch. Thank you both for info and guidance :).

Rhinoceros commented on 2018-01-16 22:22 (UTC)

@clearmartin I'd make epoch=1 [a]. A change of source is the archetypal reason to bump the epoch.

@JonnyRobbie pkgrel won't do anything if pkgver is lower. The latter has higher priority.


JonnyRobbie commented on 2018-01-16 17:57 (UTC)

I'm sorry, I didn't notice you added a pkgver() here. I don't think you had a pkgver() when it was hosted on github. Thanks for the care :)

I think your solution is pretty great. It is important that the version is monotonically increasing, which is provided with the rev-list command. It might be better to add a $pkgrel variable somewhere there so you are free to make changes to a build process and trigger an update without a change in the upstream.

clearmartin commented on 2018-01-16 17:42 (UTC)

Thanks! But that is what I already do and it is the reason why the version is now lower. The project was copied over to the new KDE repo without the history, so there is now less commits then before.

In time the number of commits overrun the previous number so one solution is to wait. Other solution is to prepend fake version (like 0.0.1.r11.6c94e5a-1) and wait for the first tag in new KDE repo. What do you think? Or is there another solution?

JonnyRobbie commented on 2018-01-16 13:49 (UTC)

It might be better to use pkgver() function in PKGBUILD when using git. See

clearmartin commented on 2018-01-15 22:44 (UTC)

Thanks for the reminder! Updated. Although that means package version is now lower but I hope it is not a problem for *-git package. Anyway if this is not right, please let me know :).

JonnyRobbie commented on 2018-01-15 22:02 (UTC)

Upstream (together with source) has changed to

Rhinoceros commented on 2017-02-21 01:46 (UTC)

No worries; it wasn't *that* late! Cheers for the response.

clearmartin commented on 2017-02-21 00:56 (UTC)

Hello, sorry for my late responses. I'll actually be happy if you maintain it. Thanks! :)

Rhinoceros commented on 2017-02-21 00:49 (UTC)

Upstream seems to be pretty good at tagging new releases. I've gone ahead and uploaded the stable package anyway. Let me know if you want to maintain it. I'm happy either way.

Rhinoceros commented on 2017-02-19 23:16 (UTC)

Hi, I was just wondering if you would be keen in adding a stable package too? i.e. not -git. Otherwise, I'm happy to add it. Cheers.

FadeMind commented on 2015-06-16 06:17 (UTC)

You have typos in conflicts/provides values. It is conflicts=("${pkgname%-*}") provides=("${pkgname%-*}") should be conflicts=("${_pkgname%-*}") provides=("${_pkgname%-*}")