So, it seems that the YunoHost team decided to change the quality checks a bit.
Last time it was automatically tested, the Streams YunoHost package got this warning:
! Using 'git clone' is not recommended ... most forge do provide the ability to download a proper archive of the code for a specific commit. Please use the 'sources' resource in the manifest.toml in combination with ynh_setup_source.
This was already there previously, but just labelled as a "possible improvement". Now, it's a warning. And because of this warning, the test score it now 6 rather than 8 it was before (8 being the best possible score you can get)(and we had it!).
So, if I want to go back to the most appealing score, I'd have to revert back to the way YunoHost packages usually fetch code, downloading tarballs from the apps upstream repos. This would mean losing the automatic daily updates. And the ability to switch to the dev branch. If you put it that way, changing to the "regular" way doesn't sound too nice.
But...
YunoHost is, I think, intended for users that are not necessarily looking for a system they need to understand in all its complexity. So, do they need the very last code updates in nearly real-time? Probably not. Do they need to run the dev version of the code? Even less.
Also, if I'm not mistaken, a kind of upstream source autoupdate feature was added to the YunoHost-Apps repo a few months ago. The package repo would be able to self-update its sources when the app upstream repo is updated.
So... I don't know what's best. Keep things the way they are, or switch back to a more conventionnal YunoHost packaging option. This would help getting the perfect score for the package, which
might encourage people to give Streams a try.
I'm not a real fan of polls, so I'm not gonna publish one, but I'd really appreciate comments on this. Just to have other people's thoughts. Right now, I'm thinking that switching back to the tarball option would be the best choice. Let me know if you think it's a good idea or not.
