Hmm. AppStream is meant as a way for Upstreams to decisively present their
product in downstream software portals (eg. KDE Discover, GNOME Software) - the
.xml is not carrying any information that is to be changing downstream (the
pkgname that was in the pullreq was an error and I believe this has since been
fixed)
You might also have heard about snappy and flatpak - two methods currently
worked on in producing 'bundled' applications. This can be 'on your own' infra
or, more likely to happen, in a cross-distro appstore like setup ('store does
not mean commercial here, allthough these options might be arising too).
flatpak for sure is basing it's application presentation on the .appdata.xml
files - snappy is likely to follow suite....
Those cross-distro app-stores would give you even more power over reaching the
users with updates at the time you want them to happen, no longer having to
wish for goodwill from random distribution projects... having your leg-work
done in preparation for this can only be beneficial for you.
Regarding your question about the screenshots: they are meant to only show your
application. Of course you can have different window styling, depending on the
desktop environment you run in, but this is by far not as important as being
able to show ANYTHING to your user what they can expect. Of course a 'KDE
Application' will likely be shown with upstream KDE styling, GNOME Apps with
upstream GNOME Styling... you can present your app in a way that makes users
want it.
Distributors are there to help you GET the application to the user...
convincing the user that YOUR project is the right one to use is your task (and
appdata.xml helps you to present you product)
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/1142#issuecomment-233933763
