raspicast
raspicast copied to clipboard
HaarigerHarald
Please provide the APK for non-Googlers
Would you consider providing the app outside of Play Store, so those on "Google-free" devices can obtain and use it? One way would be tagging releases and attaching the APK there – another to apply for F-Droid inclusion. Thanks in advance!
@HaarigerHarald any chance you could add Fastlane structures here in the app's repo (at least with summary & description, ideally also with some screenshots) so F-Droid can pick it from here? That would leave you in full control of it, and also is the only way to get graphics (screenshots, icon etc) in. You know: picture, 1000 words, first impression and all that :wink:
@IzzySoft I'll see if I can find time for it to copy the stuff over from the play store entry.
That'd be great! Feel free to ping me for a cross-check before tagging then (F-Droid will need tags to know which commits to pick up for builds).
@IzzySoft I've checked in everything I could find. Shall I publish a tag now?
Just checked: looks good, go ahead! Once the tag is there, I'll trigger a rescan at the RFP if you let me know.
Once the tag is there, I'll trigger a rescan at the RFP if you let me know.
I just figured it is there (you forgot to "let me know" :see_no_evil:). The bot now gave its thumbs-up. Are you still maintaining the app, so we shall go on? I see there was no activity here since last August – but that could also just mean it's "feature-complete" and there were no actions needed currently :wink:
@HaarigerHarald any chance for an answer – or is this app indeed no longer maintained? Due-date of the RFP has been reached again. As it doesn't make much sense to add "dead bones" to the repo, a response would be much appreciated :wink:
@IzzySoft sorry, well since the OpenMax API is basically dead on the Raspberry Pi it would only work on 32bit OS' that still have the required libraries and can install omxplayer. I'd therefore consider it somewhat legacy but it might be useful for some people, not sure.
Well, it's your app and your RFP – so the decision is yours. If you say it makes no sense, we can simply close it – no bad feelings. But if you think it might still be useful for legacy devices, and want the RFP processed: will you keep maintaining the app ("passive" maintenance is fine, i.e. fixing bugs when reported, answering issues when raised – it's clear there won't be much further development under these circumstances)?
@IzzySoft then you can include it, there might be people out there for whom it may be useful. I also just added a legacy notice to the description.
Marked the RFP ready for processing then, thanks! One last question: should we try for reproducible builds (so that the APK you've built and signed would be distributed by F-Droid, enabling you to ship quick fixes as direct updates when needed, and allow whoever already has it installed from e.g. Play to cross-update)? That would also need that APK from you to be e.g. attached to the release. It's not mandatory, but recommended.
@IzzySoft I feel like this might not be working due to the now wonky method (pre android keystore) of adding additional protection to the the ssh password storage.
Well, no bad feelings if you changed your mind and I shall simply close the RFP/MR at F-Droid, you only need to say which way you want it. If chances that it still works are rather low, maybe we better do not include it there, I agree. Again, it's your decision.
OK, and start with the latest commit (so fastlane is included) – or will you tag a new release (latest one is almost a year old now)?
Apart from fastlane descriptions there were no changes. If you build the app from main it should be functionally identical to the one published on the play store i.e. 1.4.15, thus no new release is required IMHO.
That can be done of course. Want to give it a try yourself? Here's a quick guide to help you out then.