Package Details: pkgtop 2.0-2

Git Clone URL: https://aur.archlinux.org/pkgtop.git (read-only)
Package Base: pkgtop
Description: Interactive package manager & resource monitor (stable version)
Upstream URL: https://github.com/keylo99/pkgtop
Keywords: package-manager pacman pkgtop resource-monitor
Licenses: GPL3
Conflicts: pkgtop-git
Provides: pkgtop
Submitter: MagicAndWires
Maintainer: MagicAndWires
Last Packager: MagicAndWires
Votes: 3
Popularity: 2.065670
First Submitted: 2019-08-30 23:21
Last Updated: 2019-09-20 23:09

Dependencies (1)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

MagicAndWires commented on 2019-09-20 23:09

@uffe Thanks for the tip, they must have changed the tag commit

uffe commented on 2019-09-18 09:45

pkgtop 2.0-1 PKGBUILD has checksum mismatch

MagicAndWires commented on 2019-09-11 00:00

@KeyLo99

Sorry, I got notified about this comment but then sort of forgot about it.

For your git package the pkgver will automatically get updated when running makepkg but you'll still have to update the PKGBUILD (and .SRCINFO) manually for it to show up on the AUR page. You'll have to think about how often you'll want to do this but generally I find updating for new releases and app breaking bugfixes to be a good policy.

If a development package breaks on someone's system it's their responsibility to manually update/reinstall it to make sure the issue hasn't been fixed already.

For this package it's all manual and It'll really only update for new releases, and hotfixes. I basically update as fast as I'm notified through github of new releases and am able to update things.

k399 commented on 2019-09-03 14:51

Is it automatically updating the package version depending on the release tag?

MagicAndWires commented on 2019-09-02 00:29

@BrianAllred

Odd as I couldn't seem to reproduce it on my machine yesterday, though admittedly I didn't try it in a clean chroot though, as I didn't have time for that.

Should be fixed now.

BrianAllred commented on 2019-09-01 19:20

@MagicAndWires

Yeah, it's still broken, and manually setting the variable still works.

jpegxguy commented on 2019-09-01 17:32

Thanks. Useful program!

MagicAndWires commented on 2019-09-01 15:31

@jpegxguy

Thanks for the tip! Having no personal experience with go I did not know this was something to be worried about. I assumed it downloaded any dependencies it needed within the pwd or a cache directory like most package managers do.

Should be fixed now though.

jpegxguy commented on 2019-09-01 12:45

There is a way to stop the go folder appearing in $HOME. Plese do export GOPATH="$srcdir" before the go build command.

MagicAndWires commented on 2019-08-31 22:24

@BrianAllred

Does building still fail with 1.5? I'm far from an export on go but after looking into what the variable does it should probably be fixed with the latest commit.