support chroot(relative_path_to_current_root)

[Hax4us]

It will fix this issue Hax4us/TermuxAlpine#1

[michalbednarski]

Thanks for pull request but I'm unable to see difference as chroot with relative path appears to be supported already. I've tested with termux-chroot with -0 option added to call and got successful result for all of those paths (Current dir is /home (a.k.a /data/data/com.termux/files/home), root is /data/data/com.termux/files):

..
../data/data/com.termux/files
/
/data/data/com.termux/files

As well as following after cd /data/data

./com.termux/files
com.termux/files
../..

Have I missed some case where chroot didn't work before and now works?

[SaavdhaanCyber]

translate(".") returns "/." rather than "/", when cwd is "/"
Which causes

/ # apk add zsh
(1/4) Installing ncurses-terminfo-base (6.0_p20170930-r0)
(2/4) Installing ncurses-terminfo (6.0_p20170930-r0)
(3/4) Installing ncurses-libs (6.0_p20170930-r0)
(4/4) Installing zsh (5.4.2-r0)
Executing zsh-5.4.2-r0.post-install
ERROR: zsh-5.4.2-r0.post-install: script exited with error 127
Executing busybox-1.27.2-r6.trigger
ERROR: busybox-1.27.2-r6.trigger: script exited with error 127
1 error; 17 MiB in 15 packages

[SaavdhaanCyber]

https://github.com/alpinelinux/apk-tools/blob/5f7dcadc691f4064464be02427fa6e7fd61888f1/src/database.c#L1930

[michalbednarski]

Thanks, now I could test it and appears to be working fine. I'm still working on other issues that are open but it'll take some time, so I'll be making now release with your fix.

[Neo-Oli]

Does this fix only work when /data/ is mounted? I am running into the same issue as Hax4us/TermuxAlpine#1, but I remove -b /data/data/com.termux/files/home from the proot command.

[gauloics]

still got busybox error on i686,
ERROR: busybox-1.28.4-r1.trigger: script exited with error 127