Package Details: pkgtop 2.4-1

Git Clone URL: https://aur.archlinux.org/pkgtop.git (read-only, click to copy)
Package Base: pkgtop
Description: Interactive package manager & resource monitor
Upstream URL: https://github.com/orhun/pkgtop
Keywords: package-manager pacman pkgtop resource-monitor
Licenses: GPL3
Submitter: MagicAndWires
Maintainer: orhun
Last Packager: orhun
Votes: 3
Popularity: 0.000000
First Submitted: 2019-08-30 23:21 (UTC)
Last Updated: 2020-11-25 15:52 (UTC)

Dependencies (1)

Required by (0)

Sources (1)

Latest Comments

orhun commented on 2020-08-07 20:40 (UTC) (edited on 2020-09-18 18:25 (UTC) by orhun)

Source url changed to https://github.com/orhun/pkgtop

MagicAndWires commented on 2019-11-03 15:54 (UTC)

@ava1ar

It's to allow for the RELRO and PIE build flags to be enabled. It's part of the Go package guidelines and creates more secure binary executables.

With these flags being the Arch Linux standard it's indeed a bit weird that these flags aren't enabled in the standard go package but that's an upstream issue.

ava1ar commented on 2019-10-22 18:54 (UTC)

Why this depends on go-pie, not regular go? Builds and works with regular go fine.

MagicAndWires commented on 2019-09-30 19:52 (UTC)

Right, thanks, I'll fix that.

Bit weird that git isn't mentioned as a (opt) depend for go then though. Seems like the better solution.

BrianAllred commented on 2019-09-30 17:15 (UTC) (edited on 2019-09-30 17:17 (UTC) by BrianAllred)

It requires git to build because go get uses git internally.

When I run in a clean chroot, for example:

go: missing Git command. See <https://golang.org/s/gogetcmd>
package github.com/atotto/clipboard: exec: "git": executable file not found 
in $PATH
go: missing Git command. See <https://golang.org/s/gogetcmd>
package github.com/dustin/go-humanize: exec: "git": executable file not 
found in $PATH
go: missing Git command. See <https://golang.org/s/gogetcmd>
package github.com/gizak/termui/v3: exec: "git": executable file not found 
in $PATH
package github.com/gizak/termui/v3/widgets: cannot find package 
"github.com/gizak/termui/v3/widgets" in any of:
        /usr/lib/go/src/github.com/gizak/termui/v3/widgets (from $GOROOT)
        /build/pkgtop/src/gopath/src/github.com/gizak/termui/v3/widgets 
(from $GOPATH)
==> ERROR: A failure occurred in build().

MagicAndWires commented on 2019-09-30 16:19 (UTC)

@BrianAllred This package doesn't use git, it just gets the latest release archive from the GitHub page.

BrianAllred commented on 2019-09-30 16:02 (UTC)

git isn't part of base-devel, so it needs to be in the make deps. Fails to build in a clean chroot, otherwise.

MagicAndWires commented on 2019-09-20 23:09 (UTC)

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

uffe commented on 2019-09-18 09:45 (UTC)

pkgtop 2.0-1 PKGBUILD has checksum mismatch

MagicAndWires commented on 2019-09-11 00:00 (UTC)

@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.

op_old commented on 2019-09-03 14:51 (UTC)

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

MagicAndWires commented on 2019-09-02 00:29 (UTC)

@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 (UTC)

@MagicAndWires

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

jpegxguy commented on 2019-09-01 17:32 (UTC)

Thanks. Useful program!

MagicAndWires commented on 2019-09-01 15:31 (UTC)

@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 (UTC)

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 (UTC)

@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.

BrianAllred commented on 2019-08-31 04:16 (UTC)

Build fails if $GO111MODULE is set to on. Temporarily setting it to off works, might need to put that in the pkgbuild.