#27539: Create plan for releasing on F-Droid -------------------------------------------------+------------------------- Reporter: sysrqb | Owner: tbb- | team Type: enhancement | Status: new Priority: Medium | Milestone: Component: Applications/Tor Browser | Version: Severity: Normal | Resolution: Keywords: tbb-mobile, TorBrowserTeam201902, | Actual Points: TBA-8.5 | Parent ID: #26318 | Points: Reviewer: | Sponsor: | Sponsor8 -------------------------------------------------+-------------------------
Comment (by boklm): Replying to [comment:14 sysrqb]: > I currently have a metadata file ready and it successfully builds tor browser using tor-browser-build within a fdroidserver instance I installed locally. My main worry here is how long the build process takes. On a bare-metal older laptop I'm using, the entire build process for armv7 takes roughly 3.5 hours. I'm under the impression F-Droid use VMs for each app build, and there's an upper bound of 7 hours(?) per build. If this is true, then I won't be surprised if we hit that timeout limit. One of the main reasons for this is artifacts are not cached across builds - so all repos and files are cloned/downloaded for every build iteration. I understand why this is important for a general apk builder, but this is painful for a large project like tor browser. I'm wondering if there could be an option in the F-Droid build to save some files at the end of a build, and restore them when starting a new builds. I think the directories we would want to keep are `out/`, `git_clones/`, `gclient/`. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27539#comment:15> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs