Add content-rating and releases to appdata

[PunkPangolin]

I know you didn't want this in #898, but Flathub now requires both a content rating and release information in the app data file.

Since the app itself does not include any content, I did not add content tags. In that regard, I would argue that it is comparable to a web browser or PDF viewer.

[greg-hellings]

Is there any way to make at least the value of the release attribute dynamically inserted by the build process?

Also, what is the meaning of "oars-1.1"?

[PunkPangolin]

Is there any way to make at least the value of the release attribute dynamically inserted by the build process?

This should be possible (right now the build seems to add translations into the file?), but I don't know how to write CMake builds; I only stumbled upon this when updating the Flatpak and wanted to upstream the fixes.

Also, what is the meaning of "oars-1.1"?

"OARS-1.1" rates the content of the application according to the Open Age Ratings Service. This includes tags for depictions of violence, for example. The Bible itself contains much of the content that should be tagged according to OARS, but I am unsure whether that applies to the app. In the one-liner in the PR, no content is tagged.

[greg-hellings]

Is there any way to make at least the value of the release attribute dynamically inserted by the build process?

This should be possible (right now the build seems to add translations into the file?), but I don't know how to write CMake builds; I only stumbled upon this when updating the Flatpak and wanted to upstream the fixes.

We would want to tie in with that CMake process, so that we do not need to manually update the version there when a new release is cut.

Also, what is the meaning of "oars-1.1"?

"OARS-1.1" rates the content of the application according to the Open Age Ratings Service. This includes tags for depictions of violence, for example. The Bible itself contains much of the content that should be tagged according to OARS, but I am unsure whether that applies to the app. In the one-liner in the PR, no content is tagged.

Ah, I see, that's just saying any content tagged would be using this version of the spec. I misinterpreted that as saying the oars-1.1 was an actual rating itself. Got it.