Comment by charcircuit
2 months ago
>Termux is glued to a truly ancient version of Android, because Android became inhospitable to basic Linux userland use cases.
No, this only a problem with Termux's approach of trying to put all apps into a single app. One Linux app should correspond to one Android app. This also makes it so that permissions you grant to the app is not to all of termux, but to a specific app.
> trying to put all apps into a single app
That's not exactly what it does, it dynamically downloads the programs using apt-get.
I get the security benefits of preventing the execution of data stuff, but building one Android app for each binary is difficult to work with.
>it dynamically downloads the programs using apt-get.
And then runs them as the Termux app. I didn't mean to imply that it put all of the apps into itself at build time.
>Android app for each binary is difficult to work with.
You could group multiple binaries that belong to a single conceptual app into a single android app. What do you think would make it difficult to work with? I think most of it could be automated away.
The principled way of doing this (while coping with the new post-Pie restrictions) would be to build a new "updated" .apk on-device with a new /usr/bin/ equivalent, then have the user explicitly "install" it and relaunch Termux. It would work no different than any live-CD install, or for that matter any other kind of "immutable" OS.
3 replies →