termux/dev

Discuss core development of Termux | posts by @GrimlerBot are from #termux/development on freenode

GrimlerBot

@GrimlerBot

<Archenoth> It ptraces a couple syscalls that would otherwise get SECCOMP'd

<Archenoth> And since it's statically compiled, the rest of the library issues that would normally stop this from working are actually completely absent

<Archenoth> The wrapper, strictly speaking isn't even required since you can use proot with it directly to get past seccomp, but it's a heck of a lot nicer on battery life

Prakhar Shukla

@imprakharshukla

@xeffyr Can you elaborate on the play store or basically package installation userflow with both the ways so I can add that? I'm free for a couple of hours.

Leonid Pliushch

@xeffyr

Refer to this:

startActivity(new Intent(Intent.ACTION_VIEW, Uri.parse("market://details?id=net.termux.{package name}")));

As I wrote before, installing packages from Google Play is basically opening a Google Play page with intent.

You can't do more, i.e. force Google Play to automatically install package.

Prakhar Shukla

@imprakharshukla

@xeffyr I know I how I can use intents but I was asking the userflow i.e. will the user decide every time if they want to install the package from PS or the repo?

or will there be a settings page or something similar

Leonid Pliushch

@xeffyr

Something like pkg install --source google-play package-name. Option source should be passed as extra data in am startservice ....

Option --source may accept either google-play (likely will be default for Google Play Termux build) or just HTTP(s) URL.

Later pkg script can be extended to read source from environment variable or config file.

Prakhar Shukla

@imprakharshukla

@xeffyr The package should be download to the root of /data/data/com.termux/cache/ ?

or any sub-folder?

Leonid Pliushch

@xeffyr

Better in subfolder, like /data/data/com.termux/cache/pkg.

Prakhar Shukla

@imprakharshukla

@xeffyr Pushed some changes. Also do read the associated comment.

Leonid Pliushch

@xeffyr

@fornwall Could you upload the v0.99 update for Termux app?

to Google Play?

GrimlerBot

@GrimlerBot

<live_the_dream> odd number is android 5 if i remember

<live_the_dream> ?

Leonid Pliushch

@xeffyr

ive_the_dream: not anymore. Android 5 no longer receives app updates.

tomty89

@tomty89

@xeffyr https://docs.gradle.org/current/userguide/gradle_wrapper.html#sec:verification

tomty89

@tomty89

@xeffyr Does f-droid only try to build once for a version? Or is there a way to make it retry?

Hmm, or is everything handled manually like a distro...

ihsakashi

@ihsakashi

From what I understand, moving to APK style package manager will make installing dependencies super tedious

Could there be a flag to install packages in background with Sudo? Like Lucky patcher?

We can even set termux as device manager but I don't see that happening

Leonid Pliushch

@xeffyr

Could there be a flag to install packages in background with Sudo?

We can do that, but not now.

We can even set termux as device manager but I don't see that happening

That won't happen.

GrimlerBot

@GrimlerBot

<live_the_dream> rust update is broken

<live_the_dream> can't find crate for std

<live_the_dream> so rust package is mising rustc

Prakhar Shukla

@imprakharshukla

@xeffyr Any updates for the PR?

Leonid Pliushch

@xeffyr

termux/termux-app@8d83a39

ihsakashi

@ihsakashi

Yea that sounded super unlikely

So i've got termux bootstrap on android itself, everything works it installs from ramdisk.

Only problem is apt runs with the no root patch. so now i've added an override option to generate-bootstraps.sh and plan to add apt myself

last thing, if i remove the patch from termux-packages is that all i have to do?

i still dont understand how patching works in termux..

Leonid Pliushch

@xeffyr

Only problem is apt runs with the no root patch. so now i've added an override option to generate-bootstraps.sh and plan to add apt myself

Bootstraps and no-root apt patch have no relation. One can be changed without other and vice-versa. Apt is already part of bootstrap installation.

last thing, if i remove the patch from termux-packages is that all i have to do?

Remove patch.
Compile package and copy to device.
Install package with dpkg -i.

ihsakashi

@ihsakashi

ah so all i have to do is remove the patch!

that seemed too easy..

ihsakashi

@ihsakashi

yea the bootstrap part i wanted to replace the apt included so after i compile im making it include my apt

RalfWerner

@RalfWerner

@xeffyr I have unresolved questions and hope you can help me. The ←win bug persists and files.so must also be converted with dos2unix to get correct nl/-symlinks with bash. Termux (u/) only contains symlinks.so after boot/reset. With /system/bin the ←bug can be fixed and symlinks checked:

PATH=/system/bin;l=/data/data/com.termux/lib; ln -s ../usr u;ln -s $l nl; cp nl/files.so f; dos2unix f
find u/ -type l>1;for i in $(cat $l/symlinks.so|sed s%←.%@%);do echo u${i#*@}>>2;done;diff 1 2
while read -r i;do f=u/${i#*\?}; d=`dirname $f`; [ ! -d $d ]&& mkdir -p $d; ln -s $l/${i%\?*} $f;done<f

In the meantime I have a real device with Q/10 (Galaxy Tab S6 Lite) and check a99/b99 which corresponds to termux-99 with targetSdk: 28/29 with two arch: i686/aarch64 = pixel/samsung. I have no problem with a99 but unfortunately some assumptions from the emulator checks are wrong with b99 and the (google) file app has no access to termux data at Samsung. So after setup-storage and with 29 none of the symlinks can be read. The bug has been fixed for 28 and 30.
Question: How do I get the nl/ symlink? The nativeLibraryDir is at Pixel ../../lib or /data/data/com.termux/lib. With Samsung this is missing and pm path is no longer possible - Why?

Leonid Pliushch

@xeffyr

@RalfWerner Windows support question is to @fornwall. I do not work on Windows and have no desire/opportunity to mess with it and its CRLF/LF issues - Wontfix from my side.

pm path is no longer possible - Why?

Higher Android versions + more security = more restrictions + more commands no longer working.

Termux has nothing to do with pm.

In general, pm as well as many other stuff from /system/bin should work only in ADB.

These utilities are for debugging & development purposes only and shouldn't be accessible by normal (say "untrusted") applications.

RalfWerner

@RalfWerner

@xeffyr The ←win-bug is fixed with the workaround above (on pixel). But not my question about the Samsung nl/ symlink and also not why the devices behave differently with the same build (line 46)? In a99 the symlink would not be necessary, but it is still generated in pixel. What would an Os.symlink (path, path) look like that did that?

ihsakashi

@ihsakashi

The no sandbox user '_apt' on the system i can ignore right

Where communities thrive

People

Repo info

Activity