Closed JakeSmarter closed 4 months ago
FYI: Personally, I would have gone with
io.github.TheForceEngine
for the component id because it would have resembled the spec’s intention much closer. But, with Flathub’s already existing install base we would not want to “open a new can of worms”.
I actually initially submitted my PR for the Flathub build with that id, but as github.io
is not owned by the project, Flathub's reviewers requested I add a fourth component to the id to distinguish it from any other projects that may be under the TheForceEngine
org.
Yeah, Flathub operators sometimes insist on strange decisions. Any mods would have passed as io.github.TheForceEngine.ModName
or io.github.TheForceEngine.Mod.Name
. But hey, they are the gate keepers, hence I have given up arguing with them. :shrug:
Anyway, thank you @fpiesche for maintaining the Flathub release. :+1:
Thank you @luciusDXL! :+1::smile:
application
element in favor of thecomponent
element with an appropriatetype
attributedeveloper_name
element in favor of thedeveloper
elementurl
typessuggests
,recommends
,provides
, andcontrol
elementscategories
with Desktop Entry’sCategories
See also flathub/io.github.theforceengine.tfe#3 and flathub/io.github.theforceengine.tfe#8.
FYI: Personally, I would have gone with
io.github.TheForceEngine
for the component id because it would have resembled the spec’s intention much closer. But, with Flathub’s already existing install base we would not want to “open a new can of worms”.