Search Criteria
Package Details: wtfutil 0.41.0-4
Package Actions
Git Clone URL: | https://aur.archlinux.org/wtfutil.git (read-only, click to copy) |
---|---|
Package Base: | wtfutil |
Description: | Personal information dashboard for your terminal |
Upstream URL: | https://wtfutil.com |
Keywords: | dashboard |
Licenses: | MPL2 |
Submitter: | Sweenu |
Maintainer: | yochananmarqos |
Last Packager: | yochananmarqos |
Votes: | 11 |
Popularity: | 0.000000 |
First Submitted: | 2018-05-31 18:37 (UTC) |
Last Updated: | 2022-03-18 15:19 (UTC) |
Latest Comments
troyengel commented on 2020-08-06 14:30 (UTC)
(preface: I know little about Go) It looks like Arch changed, when you attempt to install
go-pie
it now triggers the install ofgo
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. https://wiki.archlinux.org/index.php/Go_package_guidelinesMaking these two changes (remove makedepends, adding -buildmode=pie) seems to have produced a working binary for me. https://bugs.archlinux.org/task/60928 is where I found them talking about this change.
yaakushi commented on 2020-04-19 18:29 (UTC) (edited on 2020-04-19 18:29 (UTC) by yaakushi)
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 printeddev (dev)
. Now it should properly output$pkgver (${build date})
.yochananmarqos commented on 2020-03-16 19:19 (UTC)
Please add the
README
,CHANGELOG
and sample configs:dangersalad commented on 2019-09-21 18:38 (UTC)
OK, thanks for the explanation.
yaakushi commented on 2019-09-20 17:36 (UTC) (edited on 2019-09-20 17:37 (UTC) by yaakushi)
@dangersalad: According to Arch's Go packages guideline [1]:
"There are two go packages in the repositories that you can build towards;
go
andgo-pie
. All packages should preferably be built towardsgo-pie
as this enables us to deliver secure binaries. However, as upstream might have bugs, building towardsgo
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?
[1] https://wiki.archlinux.org/index.php/Go_package_guidelines
dangersalad commented on 2019-09-20 17:33 (UTC)
Is there a reason to change from
go
togo-pie
?Kunda commented on 2019-09-19 14:43 (UTC)
@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 (UTC)
@Kunda Update
go
to1.13
Kunda commented on 2019-09-19 11:02 (UTC)
Running Manjaro 18.1.0
yaakushi commented on 2019-09-19 04:44 (UTC)
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 theGOPROXY
export before callinggo build
. Thank you for the help! I've made some small changes to it and listed you as a contributor.yochananmarqos commented on 2019-09-18 20:54 (UTC)
matthias.lisin: How's this?
matthias.lisin commented on 2019-09-18 19:22 (UTC) (edited on 2019-09-18 19:24 (UTC) by matthias.lisin)
@yochananmarqos I don't think this is the way to go. Even though you download the .tar.gz source, you then redownload the package using
go get
.This does not use the source. It downloads the latest revision from Github.
Edit: Also, it's not reproducible. See Go packaging guidelines#Flags and build options
yochananmarqos commented on 2019-09-18 17:55 (UTC)
@yaakushi: Here you go. You may add me as a Co-Maintainer or Contributor if you'd like.
matthias.lisin commented on 2019-09-18 16:28 (UTC)
@yaakushi No problem, go for it. There were a few days of silence which made me worry a bit. Good to hear that you're working on the package.
yaakushi commented on 2019-09-18 14:35 (UTC)
I've been fiddling with the PKGBUILD in order to make this package build from the source instead of just fetching the binaries. I've been a bit short on time, this is why this hasn't been updated yet. Sorry.
@matthias.lisin I did. I have no idea about how people at Arch/the AUR feel about someone adopting a package someone else filled a orphan request for, and, honestly, I hadn't considered that until I read your comment. If that's frowned upon, I'd be more than happy to transfer the maintainership of this package to you. Sorry about how inconsiderate I was.
matthias.lisin commented on 2019-09-18 10:11 (UTC)
@juantascon It was orphaned, but yaakushi grabbed it instantly.
juantascon commented on 2019-09-18 08:28 (UTC)
since this was never orphaned, and since the pkgname is wrong either way as per the guidelines, I've made a new pkg: wtfutil-bin
matthias.lisin commented on 2019-08-31 18:53 (UTC)
@Kunda Already did a few days ago.
https://lists.archlinux.org/pipermail/aur-requests/2019-August/033355.html
Kunda commented on 2019-08-31 18:47 (UTC)
And here it is for 0.21.0
Kunda commented on 2019-08-31 18:36 (UTC)
Can someone please send a request to the aur-request list[1] to orphan this package and then claim new maintainership ?
[1] https://mailman.archlinux.org/mailman/listinfo/aur-requests
bjesus commented on 2019-08-28 10:12 (UTC) (edited on 2019-08-28 10:13 (UTC) by bjesus)
And here it is for 0.20
stooj commented on 2019-08-01 11:09 (UTC)
pkgbuild for the current version:
StephenBrown2 commented on 2019-01-21 17:42 (UTC)
The GitHub repo has changed to https://github.com/wtfutil/wtf
yochananmarqos commented on 2019-01-19 15:28 (UTC)
This package should be called
wtfutil-bin
since it's the binary release. That way, another package could be added that builds from source.rstacruz commented on 2019-01-08 03:24 (UTC) (edited on 2019-01-08 03:24 (UTC) by rstacruz)
Updated values for 0.4.0:
Sweenu commented on 2018-06-05 06:41 (UTC)
I don't know which fonts you are talking about. If you need emoji support, install the noto-fonts-emoji package :)
patrickelectric commented on 2018-06-04 19:48 (UTC)
Add fonts please.