Search Criteria
Package Details: so 0.4.10-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/so.git (read-only, click to copy) |
|---|---|
| Package Base: | so |
| Description: | A terminal interface for StackOverflow |
| Upstream URL: | https://github.com/samtay/so |
| Licenses: | MIT |
| Conflicts: | so-bin, so-git |
| Provides: | so |
| Submitter: | samtay |
| Maintainer: | samtay |
| Last Packager: | samtay |
| Votes: | 6 |
| Popularity: | 0.000000 |
| First Submitted: | 2020-07-07 02:16 (UTC) |
| Last Updated: | 2024-10-03 02:42 (UTC) |
Dependencies (3)
- openssl (openssl-gitAUR, openssl-staticAUR)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rust, rustup) (make)
- rust (rust-nightlyAUR, rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup) (make)
Latest Comments
samtay commented on 2022-08-21 17:57 (UTC)
Hey @m040601 I finally got around to this. I had to switch over to GitHub Actions cause Travis was rate limiting me, but now there are arm7 & aarch64 bins available:
https://github.com/samtay/so/releases/tag/v0.4.7
I also released a so-bin pkg on the AUR https://aur.archlinux.org/packages/so-bin if you use arch on your raspberry pis.
samtay commented on 2022-03-01 01:51 (UTC)
Hey thanks for the kind words. I actually thought the interface theoretically would be a good UX when developing it, but I find it a bit clunky in practice. I just haven't had time to really re-think and re-do it. So, it's great to hear that you like it as is!
You are correct that I'm not using github workflows, however I am not making those binaries by hand, I'm using appveyor for Windows and travis for the others. I did not write these myself, rather I took them from https://github.com/japaric/trust/.
In theory, I should be able to just as easily make binaries for the arm architectures listed here: https://github.com/japaric/trust/#linux-1
However, sometimes it's not quite as simple, for example I couldn't get the freebsd target working due to some SSL lib error. So, I will try, and hopefully it'll work and if so I'll just automate those onto the release artifacts like the others.
I actually thought I did have a so-bin package, but I guess I forgot to create it. I just need to find a good example and copy it, since I don't have a ton of experience creating these PKGBUILDs. Shouldn't be hard.
I'm fairly busy at the moment but I will try to get these two things completed. Feel free to open a PR or make your own so-bin package if I'm taking too long!
m040601 commented on 2022-02-26 12:27 (UTC) (edited on 2022-02-26 12:51 (UTC) by m040601)
Thank you for this tool and maintaining the PKGBUILD.
Nice to see a new release. And that it keeps getting maintained. You can be sure that this is very usefull for us end users. Pitty it's not better known.
So clean and well thought interface. For someone who says "beginner in Rust", you sure got the usability right. Really underrated.
The only thing I dont like, is the name you choose. "SO" is too short. Sooner or later is gonna clash with something else. Anyways ...
I have a question about a possible "so-bin" version and binaries for arm (raspberry pi's and chromebooks).
I always get jealous when I see those tools based on go, like yay, fzf etc. They are an easy peasy to compile and distribute binaries for a lot of platforms. They make use of the free github automatic workflows to build the binaries for release in "github realeses". And you always get a ready made "yay-bin" or "xxx-bin" PKGBUILD on AUR, and, available not only for your PC (x86). But also for my tiny raspberry pi and chromebooks running Archlinux ARM. I dont want to download Go or Rust and compile on them.
I dont know Rust or Go. But I understand that Rust is not as easy to compile as Go. But I also see other Rust projects on github making use of the github workflows, like "fd" or "xsv" etc.
I only see x64 binaries released on https://github.com/samtay/so/releases/.
And I dont see any use of the build workflows in https://github.com/samtay/so/tree/master/.github/workflows
So I assume you are still building the binaries "by hand". Am I correct ?
My question is.
Would it be a lot of work or very difficult to also build for arm ? (2 packages one universal "arm" (for armv7h, armv6 etc) and one universal "aarch64" (for armv8)
This would be so usefull for text browsing in the underpowered raspberry pi's and chromebooks.
Since you already maintain the "so" and "so-git" PKGBUILDS, could you also provide a "so-bin" PKGBUILD ? At least for x64 ?
Thanks in advance