6 ms·
The GitHub discussion is significantly more informative and carries a lot of thinking behind the changes: https://github.com/termux/termux-app/issues/1072 https
by izacus 6y ago
The GitHub discussion is significantly more informative and carries a lot of thinking behind the changes: https://github.com/termux/termux-app/issues/1072 https://github.com/termux/termux-app/issues/1072
IMO a better link than a short paragraph on Wiki.
- westurner 6y agoNote that there are 297 hidden items in that issue so you have to click "Load more..." ceil(297/60) times to read all of the comments about how APK packaging is soon necessary for latest Android devices so the termux package manager can't just dump executable binaries wherever. FWIU: - Android Q+ disallows exec() on anything in $HOME, which is where termux installed binaries that may have been writeable by the executing user. - Binaries installed from APKs can be exec()'d, so termux must keep APK repacks rebuilt and uploaded to a play store. - Termux shouldn't be installed from Google Play anymore: you should install termux from the F-Droid APK package repos, and it will install APKs instead of what it was doing. - Compiling to WASM with e.g. emscripten or WASI was one considered alternative. "Emscripten & WASI & POSIX" https://github.com/emscripten-core/emscripten/issues/9479 https://github.com/emscripten-core/emscripten/issues/9479
- hyperpallium2 6y agoWhat about development on-the-device? - It seems C compiled with clang on the device wouldn't be executable? (If it was, that would be a way around the restriction: distribute packages as source, like the good old days) > offer users the option of generating an apk wrapping their native code in a usable way. https://github.com/termux/termux-app/issues/1072#issuecomment-475895891 https://github.com/termux/termux-app/issues/1072#issuecommen... This seems a promising solution: compile from source, create an apk, install - your custom distribution! For popular collections of packages, a pre-built apk. - Java might be explicitly blocked, being a system language for android, even though its byecode is interpeted and not exec()ed. - Other interpreted languages should be OK e.g. python
- pantalaimon 6y agoHow would binaries compiled on the device differ from those downloaded from the internet?
- deleted 6y ago[deleted]
- hyperpallium2 6y agoYeah, I think you're right: you could download instead of compile, it's just the assembling into an apk on the device that has the advantage of customizing exactly what you want.
- westurner 6y ago> > offer users the option of generating an apk wrapping their native code in a usable way. > This seems a promising solution: compile from source, create an apk, install - your custom distribution! For popular collections of packages, a pre-built apk. FPM could probably generate APKs in addition to the source archive and package types that it already supports. The conda-forge package CI flow is excellent. There's a bot that sends a Pull Request to update the version number in the conda package feedstock meta.yml when it detects that e.g. there's a new version of the source package on e.g. PyPI. When a PR is merged, conda-forge builds on Win/Mac/Lin and publishes the package to the conda-forge package channel (`conda install -y -c conda-forge jupyterlab pandas`) The Fedora GitOps package workflow is great too, but bugzilla isn't Markdown by default. Keeping those APKs updated and rebuilt is work.
- pjmlp 6y agoDEX bytecode is compiled to native code since Android 5, Android 7 introduced a multi-layer where it is intepreted only to get the first execution profile for the JIT, then the JIT gathers PGO data while executing, which will be used by AOT compiler when the device is idle, afterwards only the pure machine code binary executes until the next update, or loading code that wasn't touched by the JIT. As of Android 10, PGO data files are uploaded into the store and shared across similar devices so that the AOT compilation with PGO can be done right away on installation. Having bytecodes doesn't mean being interpreted.
- mehrdadn 6y agoAre there any SELinux + Android experts there? Do you know if there is a way to alter the policy to undo this change with root privileges without disabling SELinux enforcement entirely? It fundamentally seems like it should be possible; I just don't know how. It would get around the issue very nicely if someone can figure out how, since I imagine many people with Termux also have root.
- app4soft 6y agoSadly, since January 1st, 2020 Termux team dropped[0] support for Android 5.x/6.x, so actually in F-Droidrepo it now requires minimum Android 7.x: > Support for Android 5.x.x - 6.x.x is dropped forever. Time to upgrade your devices or learn how to backport git changes.[1] And this part from Termux devs reply is especially cynical: > ... Time to upgrade your devices...[1] It looks like they has a contract with devices manufacturers... ... No, I no need such type of "app improvements in new version" which require me to buy a new device. FTR, In F-Droid Archive[2] repo there is still Termux v0.75 for Android 5.x/6.x (which I'm using on Ido device), but it is horrible because Termux packages repo for Android 5.x/6.x are now disabled[3] too. [0] https://github.com/termux/termux-app/issues/1516 https://github.com/termux/termux-app/issues/1516 [1] https://github.com/termux/termux-app/issues/1407#issuecomment-570550054 https://github.com/termux/termux-app/issues/1407#issuecommen... [2] https://apt.izzysoft.de/fdroid/index/apk/com.termux?repo=archive https://apt.izzysoft.de/fdroid/index/apk/com.termux?repo=arc... [3] https://github.com/termux/termux-packages/issues/4467 https://github.com/termux/termux-packages/issues/4467
- driverdan 6y agoWhy would you expect them to continue supporting a 5 year old OS version?
- app4soft 6y agoBecause its community driven FLOSS project. And it would "OK" if there would no releases with new features... but bug fix releases which is worse. Instead, team (owner & core members) just dropped & disabled everything, leaving Android 5.x/6.x device owners in frozen state. Even more, team not proposed itself & ignored any proposition from others to at least support Termux for Android 5.x/6.x in LTS-way.
- bill_mon 6y agoBecause most devices can't be updated? Supporting version 4+ gives you a much larger audience than limiting to version 7+.
- 6y ago