Instaloader worked great without the dependency. I don't have an account, so it wouldn't have helped me lol. Tuir works great in mlterm on Tiger but crashes the regular terminal. Glad I have mlterm!
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Open-source software currently supported on macOS PowerPC
- Thread starter barracuda156
- WikiPost WikiPost
- Start date
-
- Tags
- opensource powerpc
- Sort by reaction score
- Status
Yeah, getting a better terminal was a necessity, not a luxury. aria2tui crashed in Apple Terminal too, for example.
Recently added ports:
1. FastAnime and viu (rebranded upgrade): streaming and download of Anime. Confirmed to work.
2. py-awscli2 (and a lot of dependencies for it): access to AWS, Linode etc. Not tested in detail, but looks like working.
3. zeek: network security monitoring tool. To be tested.
4. rb-rtfm-filemanager: TUI file manager in ruby.
1. FastAnime and viu (rebranded upgrade): streaming and download of Anime. Confirmed to work.
2. py-awscli2 (and a lot of dependencies for it): access to AWS, Linode etc. Not tested in detail, but looks like working.
3. zeek: network security monitoring tool. To be tested.
4. rb-rtfm-filemanager: TUI file manager in ruby.
mastui: TUI client for Mastodon
github.com
mastui: new port, TUI client for mastodon · macos-powerpc/powerpc-ports@3586fd8
Overlay repo with fixes to use with MacPorts on macOS PowerPC - mastui: new port, TUI client for mastodon · macos-powerpc/powerpc-ports@3586fd8
github.com
I tried to build sigil-qt4 with boost178, and got a failure. Is it related or is it possible to get this working with boost178?
P.S. Trojan builds with boost178 on Tiger, so at least sometimes changing boost version works.
P.S. Trojan builds with boost178 on Tiger, so at least sometimes changing boost version works.
Last edited:
Boost 178 is the only one that builds out of the box on Tiger. Per Kencu, the issue is not trivial to fix for Boost171: https://trac.macports.org/ticket/71753
I have a log for Boost 169 if you want to see if that is an easily fixable issue. Not much uses that boost though, so it might be better practice to migrate ports (at least Trojan) to boost178.
Edit to include boost176 log.
Last edited: