Package Details: wtfutil 0.38.0-1

Git Clone URL: (read-only, click to copy)
Package Base: wtfutil
Description: Personal information dashboard for your terminal
Upstream URL:
Keywords: dashboard
Licenses: MPL2
Submitter: Sweenu
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 11
Popularity: 0.000021
First Submitted: 2018-05-31 18:37
Last Updated: 2021-07-12 15:09

Latest Comments

1 2 3 Next › Last »

troyengel commented on 2020-08-06 14:30

(preface: I know little about Go) It looks like Arch changed, when you attempt to install go-pie it now triggers the install of go causing this PKGBUILD to fail on it's makedepends(). I dug up in the wiki (and found a go/go-pie bug to match) that now you add -buildmode=pie to your recipe instead.

Making these two changes (remove makedepends, adding -buildmode=pie) seems to have produced a working binary for me. is where I found them talking about this change.

yaakushi commented on 2020-04-19 18:29

Thanks for the patch, @yochananmarqos.

Also, sorry it took me so long to update this. Starting at 0.28.0-1, the PKGBUILD should now properly overload the build version and date (until this point, wtfutil -v just printed dev (dev). Now it should properly output $pkgver (${build date}).

yochananmarqos commented on 2020-03-16 19:19

Please add the README, CHANGELOG and sample configs:

    cd "wtf-$pkgver"
    install -Dm755 "$pkgname" -t "$pkgdir/usr/bin"
    install -Dm644 -t "$pkgdir/usr/share/licenses/$pkgname"
    install -Dm644 -t "$pkgdir/usr/share/doc/$pkgname"
    cp -r _sample_configs "$pkgdir/usr/share/doc/$pkgname/sample_configs"

dangersalad commented on 2019-09-21 18:38

OK, thanks for the explanation.

yaakushi commented on 2019-09-20 17:36

@dangersalad: According to Arch's Go packages guideline [1]:

"There are two go packages in the repositories that you can build towards; go and go-pie. All packages should preferably be built towards go-pie as this enables us to deliver secure binaries. However, as upstream might have bugs, building towards go should be a last resort."

I do realize that's mostly aimed at the prebuilt packages at the official repositories, but I figured it'd be good practice to to the same here at AUR. Am I wrong?


dangersalad commented on 2019-09-20 17:33

Is there a reason to change from go to go-pie?

Kunda commented on 2019-09-19 14:43

@matthias.lisin Oh ok, yea, manjaro hasn't caught up yet. When it does, I'll test and report back

matthias.lisin commented on 2019-09-19 11:38

@Kunda Update go to 1.13

Kunda commented on 2019-09-19 11:02

==> Validating source files with sha256sums...
    wtfutil-0.22.0.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting wtfutil-0.22.0.tar.gz with bsdtar
==> Starting build()...
flag provided but not defined: -trimpath
usage: go build [-o output] [-i] [build flags] [packages]
Run 'go help build' for details.
==> ERROR: A failure occurred in build().

Running Manjaro 18.1.0

yaakushi commented on 2019-09-19 04:44

I've bumped the package to its latest version, building from the source. It does need to set the GOPROXY env. var pointing to the GoCenter repository as described in the upstream documentation, otherwise the user wouldn't be able to fetch all of the dependencies.

@yochananmarqos Since this software is using Go mod, we don't need the prepare() bit (and we can also simplify the path inside $srcdir). Oh, and we do need to export the GOPROXY export before calling go build. Thank you for the help! I've made some small changes to it and listed you as a contributor.