
At the start of a repo update, it will create a copy of the apk table. Throughout the update, it will query the original apk table for info. All inserts and updates happen to the temp table. After the repo has been verified as trusted, the original apk table is emptied, and all apks are copied from the temp table to the real one. I realise that the work done to query the apk table for info during the update could happen against the temp table, but it was not neccesary to move all of the queries that are required for this task to the temp apk provider.
F-Droid Client
Client for F-Droid, the Free Software repository system for Android.
Building with Gradle
The only requirements are the Android SDK and Gradle 2.7:
cd F-Droid
gradle assembleRelease
Direct download
You can download the application directly from our site or browse it in the repo.
Contributing
See our Contributing doc for information on how to report issues, translate the app into your language or help with development.
IRC
We are on #fdroid
and #fdroid-dev
on Freenode. We hold weekly dev meetings
on #fdroid-dev
on Tuesdays at 20h UTC, which usually last half an hour.
License
This program is Free Software: You can use, study share and improve it at your will. Specifically you can redistribute and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
Some icons are made by Picol, Icomoon or Dave Gandy from Flaticon or by Google and are licensed by Creative Commons BY 3.0.
Other icons are from the Material Design Icon set released under an Attribution 4.0 International license.