Closed AsciiWolf closed 7 months ago
That is great, thank you for publishing!
Questions:
Hi Eric,
Thanks for the quick reply!
ad 1. It is possible for third-parties to have their own infrastructure, however it is not a common thing and I am not sure how hard it would be to set it up. You can try asking here. ad 2. Well, either the Flatpak maintainer can update the Flatpak by manually editing its (yaml) manifest file or there is something called x-data-checker bot that basically sends a new Pull Request to the Flathub app repository with updated version number, sha256 checksum, AppStream metadata version and other things when it detects a new upstream release. However, it requires specific metadata in the application Flatpak manifest file and I did not add these metadata yet. I will do it later. :-)
That sounds great. Let me know when you have the metadata plugged in and I'll take a look
I will let you know. :-) If you want, let us also know here whether you are interested in having push rights to the Xnec2c Flatpak Git repository (once it is created) so you can merge the Pull Requests and do other changes to the Flatpak.
Ok. I commented on the thread for push rights. Thanks!
@AsciiWolf, I think this issue is ready to close, but please re-open if I missed something.
Thanks!
-Eric
@AsciiWolf, we just released v4.4.13. Is there anything that needs to be done to update flathub?
@KJ7LNW I will take a look tomorrow. Thanks for letting me know!
No need to reopen this ticket. xnec2c has been on Flathub for a while now and I have created a separate ticket for the update.
got it
I have made a Flatpak build of Xnec2c that I am going to publish on Flathub. Feel free to let me know whether you are interested in co-maintaining the Flathub Flatpak and having push access to its Git repository. :-)