Is there a reason to extract tor.tar.gz into a temporary directory and then copy all of the content into service/src/main? Can we simply extract tor.tar.gz directly into service/src/main instead?
Is there a reason to extract tor.tar.gz into a temporary directory and then copy all of the content into service/src/main? Can we simply extract tor.tar.gz directly into service/src/main instead?
Yes, I think we should extract it in service/src/main directly.
Trac: Keywords: TorBrowserTeam202004R deleted, TorBrowserTeam202004 added Status: needs_review to needs_revision
Is there a reason to extract tor.tar.gz into a temporary directory and then copy all of the content into service/src/main? Can we simply extract tor.tar.gz directly into service/src/main instead?
Yes, I think we should extract it in service/src/main directly.
We have under consideration the uploading the tor packages to a central repo (like maven central). If we package directly into 'service/src/main' then that won't work cleanly with other projects that want to use tor for android.
Is there a reason to extract tor.tar.gz into a temporary directory and then copy all of the content into service/src/main? Can we simply extract tor.tar.gz directly into service/src/main instead?
Yes, I think we should extract it in service/src/main directly.
We have under consideration the uploading the tor packages to a central repo (like maven central). If we package directly into 'service/src/main' then that won't work cleanly with other projects that want to use tor for android.
The proposed patch is extracting tor to /var/tmp/dist/tor, before copying it to service/src/main. Why can't we just extract it to service/src/main? I don't think it changes anything related to maven central, it's just a simplification of tor-android-service build script.
This looks good to me. I merged this branch to master with commit acfda9f43d3203bb12913b56cbf8c3891a16253c.
I checked that it builds correctly on all android platforms. However I didn't check that the apk is working correctly.
It is not. The log says it's still the old Tor that is loaded when testing a nightly build containing all the fixes for #28704 (moved) and children. I opened #33930 (moved) for that.