Package Details: pkgtop-git 2.5.1.r0.ga367254-1

Git Clone URL: (read-only, click to copy)
Package Base: pkgtop-git
Description: Interactive package manager & resource monitor (git)
Upstream URL:
Keywords: package-manager resource-monitor
Licenses: GPL3
Conflicts: pkgtop
Provides: pkgtop
Submitter: op_old
Maintainer: orhun
Last Packager: orhun
Votes: 8
Popularity: 0.000000
First Submitted: 2019-08-26 21:20 (UTC)
Last Updated: 2023-10-13 10:59 (UTC)

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

parkerlreed commented on 2019-09-17 20:26 (UTC)

Currently the pkgver is pulling an older label than the PKGBUILD states causing infinite loop

1  aur/pkgtop-git  2.0.r0.gd16e41f-1 -> 2.0.r2.g345aaeb-1

op_old commented on 2019-08-31 11:46 (UTC)

@MagicAndWires that would be good actually. Can you give me more details? Btw I'll update the pkgver as you suggested. Thanks.

MagicAndWires commented on 2019-08-30 23:59 (UTC) (edited on 2019-08-31 00:02 (UTC) by MagicAndWires)


Additionally, if you use git describe --long --tags | sed 's/\([^-]*-g\)/r\1/;s/-/./g' for your pkgver() the created pkgver variable will include the tag as a version number, the most current pkgver in this format returns: 1.3.r0.g10ff101

Any additional revisions without a new tag would read 1.3.r01-nn until a new tag is created (bumping it to 1.4.r0).

MagicAndWires commented on 2019-08-30 23:35 (UTC) (edited on 2019-08-31 00:20 (UTC) by MagicAndWires)

I've created a stable PKGBUILD that will only update with every pkgtop release for those interested.

@KeyLo99 maybe we can coordinate and create a split package or using the same group. As far as I know though makepkg will always build all packages in a split PKGBUILD so I think just housing both PKGBUILDS under the same group is a better alternative. Let me know if you're interested in this.

op_old commented on 2019-08-27 17:12 (UTC)

Yes, I know. It's because it's not released yet. Thanks anyway.

yochananmarqos commented on 2019-08-27 16:34 (UTC)

There are no releases available on GitHub. A VCS package pulls the latest commit every time it's built, it can't have a static version number.

op_old commented on 2019-08-27 16:32 (UTC)

I've removed it on purpose. See my commit message.

yochananmarqos commented on 2019-08-27 14:33 (UTC)

No, don't remove it. Please see the VCS package guidelines.

op_old commented on 2019-08-27 13:03 (UTC) (edited on 2019-08-27 13:21 (UTC) by op_old)

@yochananmarqos thanks for following my projects. I've changed the PKGBUILD file and removed the pkgver function for more readable package version. Can you check and report if it's okay or not again?

yochananmarqos commented on 2019-08-26 23:56 (UTC) (edited on 2019-08-26 23:58 (UTC) by yochananmarqos)

Please fix the pkgver, it should be pkgver=r315.19d57fb as generated by the pkgver() array.

Also please do not use >= for go as it does not detect go-pie as a matching dependency. Everyone should be up to date and have the newest version.