7 ms·

> Some of those issues are manageable when making use of Java APIs, naturally not all of them, and even less if one refuses to touch Java. What do you mean by

> Some of those issues are manageable when making use of Java APIs, naturally not all of them, and even less if one refuses to touch Java. What do you mean by that and how does it affect not being invoke exec() in android 10 without making changes to SELinux?

pjmlp 6y ago
You don't call exec(), rather the Android Java APIs, that is the whole point that they don't want to change, more Java and less C POSIX.
- Abishek_Muthian 6y ago
  Sorry that doesn't make any sense. The whole point of Termux is to make GNU/Linux tools available on Android without root by compiling it for the Termux environment, to run those packages from the user directory it needs exec(). You seem to suggest that it rather be android packages, for that you don't need Termux in the first place.
  - pjmlp 6y ago
    It makes perfectly sense, Android OS is not GNU/Linux, the Linux syscalls never were or will ever be part of the public API. The public API is based on Java and a couple of NDK APIs, clearly enumerated by Google as stable APIs. They can either adapt themselves to this reality, make use of those APIs in a mingw like way, creating wrappers, or die in their faith that Android is Linux, alongside countless attempts to GNU/Linux phones.
    - dvdkon 6y ago
      So they can either put in a monstrous effort to end up with a worse product or not be on the Play Store. I know what I'd choose. The kind of people who want Termux are capable of downloading an APK, I wouldn't worry too much about it.
      - pjmlp 6y ago
        APKs are deprecated, replaced by Android App Bundles, adapt or die.
        dvdkon 6y ago
        You keep saying that, but I don't see Termux dying unless Google straight up disallows fork() for all apps, even old ones.
        pjmlp 6y ago
        Given that fork() isn't part of stable APIs list, it might end in seccomp list. But there is hope, just like with mingw, termux can use the OS official APIs to launch processes.

pjmlp 6y ago

You don't call exec(), rather the Android Java APIs, that is the whole point that they don't want to change, more Java and less C POSIX.

Abishek_Muthian 6y ago
Sorry that doesn't make any sense. The whole point of Termux is to make GNU/Linux tools available on Android without root by compiling it for the Termux environment, to run those packages from the user directory it needs exec(). You seem to suggest that it rather be android packages, for that you don't need Termux in the first place.
- pjmlp 6y ago
  It makes perfectly sense, Android OS is not GNU/Linux, the Linux syscalls never were or will ever be part of the public API. The public API is based on Java and a couple of NDK APIs, clearly enumerated by Google as stable APIs. They can either adapt themselves to this reality, make use of those APIs in a mingw like way, creating wrappers, or die in their faith that Android is Linux, alongside countless attempts to GNU/Linux phones.
  - dvdkon 6y ago
    So they can either put in a monstrous effort to end up with a worse product or not be on the Play Store. I know what I'd choose. The kind of people who want Termux are capable of downloading an APK, I wouldn't worry too much about it.
    - pjmlp 6y ago
      APKs are deprecated, replaced by Android App Bundles, adapt or die.
      - dvdkon 6y ago
        You keep saying that, but I don't see Termux dying unless Google straight up disallows fork() for all apps, even old ones.
        pjmlp 6y ago
        Given that fork() isn't part of stable APIs list, it might end in seccomp list. But there is hope, just like with mingw, termux can use the OS official APIs to launch processes.