[Suggestion] Prepare to deal with sailfishos/ssu PR #16

[Olf0]

DESCRIPTION

An unannounced and unreleased Sailfish OS version ("4.6") will change the way versions are handled in the ssu utility.

I imagine this may have an impact on how Installer handles/must handle OBS repository information, hence this issue.

ADDITIONAL INFORMATION

• Add major and minor release versions in repo variables sailfishos/ssu#16
• https://irclogs.sailfishos.org/logs/%23sailfishos/%23sailfishos.2024-04-11.log.html

[Olf0]

See also storeman-developers/harbour-storeman-installer#308, sailfishos-chum/sailfishos-chum-gui#270 and sailfishos-chum/sailfishos-chum-gui-installer#39.

Please use sailfishos-chum/sailfishos-chum-gui#270 as the main, tracking issue for this.

[Olf0]

This has been addressed in the SailfishOS:Chum GUI app as well as the SailfishOS:Chum GUI Installer and the Storeman Installer.

It still needs to be thoroughly checked if Storeman should to be adapted, or if it never sets or queries its own download (OBS-) repository and leaves setting this repo to the Storeman Installer (which is already adapted); in the latter case there is nothing to do than to close this issue with appropriate reasoning.

Likely that (i.e. "nothing to do") is the case, because both search terms build.sailfishos.org and build.merproject.org yield no hit in source code (only the README.md):

• https://github.com/search?q=repo%3Astoreman-developers%2Fharbour-storeman+build.sailfishos.org&type=code
• https://github.com/search?q=repo%3Astoreman-developers%2Fharbour-storeman+build.merproject.org&type=code

[nephros]

I'm going to add that this may be incoming for lesser releases also:

https://irclogs.sailfishos.org/logs/%23sailfishos/%23sailfishos.2024-10-24.log.html

... but it seems to have gone over well for 4.6, it probably will be fine for the others too.

[Olf0]

@nephros, thank you for he heads up, but all the "linking" discussed on IRC (originally for SailfishOS:Chum:Testing and now for SailfishOS:Chum) only addresses the various SailfishOS 4.x.y.z build targets of the SailfishOS:Chum(:Testing) community repository at the SailfishOS-OBS: For all other repositories there (e.g. Storeman's download repository which Storeman-Installer uses) measures to handle this issue must be employed (or not) separately.
_{NB: For some details, how the "linking" is implemented, see sailfishos-chum/sailfishos-chum-gui#287 (comment) ff.}

For Storeman's download repository I considered saving a few megabytes and compiling a single package (Storeman) for some fewer targets is not worth asking the sailor Pami Ketolainen aka @keto (or Matti Lehtimäki, @mlehtima at GitHub aka @mal) to employ links as he did for SailfishOS:Chum:Testing (and may employ for SailfishOS:Chum), as this can only be performed by an OBS-administrator.
Ultimately this implies I will keep all build targets for which a corresponding DOD repository exists at the SailfishOS-OBS and all the mappings (extra targets) (by OBS-repo "meta"-config) for SailfishOS 4.x.y.z releases for which no corresponding DOD repository exists.
Still, this is (supposedly; i.e. rather "should be") already resolved for future releases of SailfishOS, because after the transition phase covering all SailfishOS 4.6 releases, I followed the way SailfishOS:Chum adopted Jolla's new scheme for DOD repos and OBS-repos which depend on them (i.e. the 5.0_* build targets serve all SailfishOS 5.0.y.z releases).