You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ability to publish custom versions of Termux (as a new app in Play store with new name) along with a setup script (or something) that configures which packages will be installed in the environment (basically pre-creates the environment that will be built into the Android app), and finally option to have it launch a program automatically.
Reference implementation
None yet, but basically the idea is that someone could use this as a tool to, for example, ship an NW.js or Electron application to Google Play store, so that when the Termux-derivative app opens, the desired Linux-like application shows up full screen, and the user does not interact with the underlying Termux stuff (there should be no way to get out of the full-screen mode).
That was very brief, there's definitely more to it, but I wanted to get the conversation started. I wrote some ideas in the NW.js tracker, where people wish they could publish NW.js apps to Google Plya: nwjs/nw.js#94 (comment).
Publishing either Electron or NW.js apps would be a very similar process.
So basically this is a feature request to make termux-app have some scripts (or something) that make termux-app a tool for creating full-screen Android apps using familiar Linux technologies (GTK, Qt, Electron, NW.js, Chrome Carlo, etc).
The text was updated successfully, but these errors were encountered:
All packages have static prefix path which is hardcoded into binaries (that generally not our problem). Reviewing source code of each package and patching it to use "dynamic prefix" will require a lot of work.
We do not allow to use our APT repositories by third party projects due to limited bandwidth.
So if you need a custom Termux app, a custom package repository should be created too.
I think the repo isnt problem as in the app publishing you as the dev are going to download the package and bundle it with the app, so there wont be drastically more users.
I won't bother create & maintain 1000+ patches in order to make packages to have multiprefix. That's not easy task, I'll have to review source code for each package. Not just to create the patch, but after each update to be sure there won't be any side effects.
So, you need to deal with packages on your own. How you do this - that's your question, not ours. We provide source code and documentation to make a complete Termux clone.
ghost
locked and limited conversation to collaborators
Oct 17, 2021
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature description
Ability to publish custom versions of Termux (as a new app in Play store with new name) along with a setup script (or something) that configures which packages will be installed in the environment (basically pre-creates the environment that will be built into the Android app), and finally option to have it launch a program automatically.
Reference implementation
None yet, but basically the idea is that someone could use this as a tool to, for example, ship an NW.js or Electron application to Google Play store, so that when the Termux-derivative app opens, the desired Linux-like application shows up full screen, and the user does not interact with the underlying Termux stuff (there should be no way to get out of the full-screen mode).
That was very brief, there's definitely more to it, but I wanted to get the conversation started. I wrote some ideas in the NW.js tracker, where people wish they could publish NW.js apps to Google Plya: nwjs/nw.js#94 (comment).
There's also a similar Electron requests: electron/electron#9162 and electron/electron#562
Publishing either Electron or NW.js apps would be a very similar process.
So basically this is a feature request to make termux-app have some scripts (or something) that make termux-app a tool for creating full-screen Android apps using familiar Linux technologies (GTK, Qt, Electron, NW.js, Chrome Carlo, etc).
The text was updated successfully, but these errors were encountered: