[Package]: proot utils (proot-apps, udocker)

[knyipab]

Why is it worth to add this package?

Some proot utils could really augment the usability of Termux and fill the gap of existing proot tool (i.e. proot-distro). I would like to draw @sylirre attention, provided your expertise and that these utils need same workarounds used in proot-distro. While proot-distro ships linux distro:

• proot-apps: ships linux apps (and install .desktop files), very much like snap and flatpak package manager
  • https://github.com/linuxserver/proot-apps
  • proot-distro is not ideal for users who need a few GUI apps that is not available in termux-packages & TUR, cuz migrating between distro version and device can be a hassle. Also, proot-distro does not integrate well (not registered in start menu) with DE by termux-packages. In contrast, proot-apps is designed to serve such purpose.
  • app images are hosted by linuxserver, a well known docker image provider, and no need for Termux org to host anything
  • I conducted preliminary test to adapt it to Termux by:
  • soft-linking jq, ncat and proot to those $PREFIX/bin instead of the one provided by proot-apps
  • Doing some similar workarounds in proot-distro
  • It can run a few apps, e.g. firefox and chromium, but some bugs persists and I am not expert in proot-distro
• udocker: ships containers, can be regarded as an implementation of docker using proot
  • https://github.com/indigo-dc/udocker
  • best for server programs
  • we all know the ease of acquiring and disposing docker containers
  • here's someone's work to port it to Termux, by applying some proot-distro's workarounds: https://github.com/George-Seven/Termux-Udocker

Termux org/dev may or may not be interested in maintaining them, and they have the potential to be in TUR. But by any chance could proot-distro be structured to have a tool that can generate suitable arguments for proot-apps and udocker? Thanks!

Home page URL

No response

Source code URL

https://github.com/linuxserver/proot-apps and https://github.com/indigo-dc/udocker

Packaging policy acknowledgement

• [X] The project is actively developed.

• [ ] The project has existing packages and is "well known".

• [X] Licensed under an open source license.

• [X] Not available through a language package manager: pip, npm, cpan, cargo, etc.

• [X] Not taking up too much disk space (< 100MiB per architecture, exceptions can be made)

• [X] Not duplicating the functionality of existing packages.

• [X] Not serving hacking, malware, phishing, spamming, spying, ddos functionality.

• [X] I certify that I have read Termux Packaging Policy and understand that my request will be denied if it is found lacking.

Additional information

No response

[SCOS100]

This seems pretty cool, and it has a use.