@JulienBlanc sorry these things are on you, afaics they all happen inside the .spec file.
Tell me when you’re done, I’ll bump the revision.
Done (outside screenshots, which i’ll need to add later). I also bumped the version to 0.2.
If you have a codeberg account, i think i can give you push access to the repo.
1 Like
@piggz Re-submitted the latest commit. Hope I did it right, I still sometimes feel like I’m winging it with OBS.
I also added the new (?) sailfishos:5.1 repositories, and they build, too.
Done.. You can now manage the app in chum:testing, then submit to chum when ready (current version is in chum already)
1 Like
Thanks again.
When did that happen? I’m not aware of submitting this to chum proper?
1 Like
I do that as part of the initial request … all future ones will be triggered by yourself
1 Like
You mean #19? Was that my initial request? No, you mean in build.sailfishos.org. I was so sure I requested chum:testing though. Did I mess up there?
You did … as part of initial submissions to chum:testing, we also then submit to chum ourselves
Are you saying it was your choice to submit it from testing to Chum proper straight away?
Yes, its standard process for the first submission, see GitHub - sailfishos-chum/main: Documentation and issue tracker for the SailfishOS:Chum community repository · GitHub
1 Like
If all is fine, the package will be promoted to the main
sailfishos:chumrepository by the SailfishOS:Chum maintainers.
Interesting, I did not know that. Well, now I do. Thanks again!
One difference I see in the recently compiled Subsoniq on ohnonot’s webserver and chum:testing, that the emblems next to the page names in the pulley menu are missing.
(screenshot taken on a build I compiled from commit 6e67baede9 on April 23rd)
Was that an intentional change?
No, clearly not intentional. I guess the migration to cmake broke the resources path, need to fix that. Thanks for reporting.
Now that the basics are working 
I wonder if it would be too much work to enable caching? The app already creates ~/.cache/harbour-subsoniq, is there something in QML/Qt that would populate it as one listens? So that already listened songs don’t have to be streamed again, ideally so that offline listening becomes possible?
(I have never coded Qt, neither QML nor C++)
That would obviously need to be implemented at the C++ level. It’s clearly feasible, but would imply that i’m not busy finished other apps that i need to publish at the moment.
PRs welcomed, as always :).
Yes, “enable” was wrong, “implement” is right.