-
-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do you mind if I write a request to be added to F-Droid? #148
Comments
I don't mind, see also https://apt.izzysoft.de/packages/eu.darken.myperm/ |
AuthorName: Matthias Urhahn
AuthorEmail: [email protected]
AuthorWebSite: https://darken.eu
Donate: https://github.com/sponsors/d4rken
SourceCode: https://github.com/d4rken-org/permission-pilot
IssueTracker: https://github.com/d4rken-org/permission-pilot/issues
Changelog: https://github.com/d4rken-org/permission-pilot/releases |
Are there any news regarding F-Droid submission? |
Hm, basically waiting for CAPod to be approved, which is waiting on someone from F-Droid for review: CAPod uses the same new build script that generates a VERSION file that F-Droid can parse for automatic builds: Once that is working, the same script could be used for all my apps to get automatic builds on f-droid. |
@d4rken for myperms, we have an issue concerning updates. Our update checker only parses the |
Permission Pilot uses the same release script as CAPod, and creates a VERSION file: Could the same solution from CAPod be used here too? |
Yes, sure! That's what I meant by "as Flutter does". A |
@IzzySoft Permission Pilot already uses the same scheme as CAPod, the VERSION file is available. What is the blocker here? Did I forget some tweak that I did in CAPod and didn't do here? π€ |
Ah, right β must have missed that. Thanks Matthias, adjusted in the RFP and marked it "ready for packaging" then. |
No description provided.
The text was updated successfully, but these errors were encountered: