Dne 17. 10. 24 v 8:45 Milan Crha napsal(a):
On Wed, 2024-10-16 at 18:53 +0200, Vít Ondruch wrote:
Maybe changing the .desktop file is harmless and good thing after
all.
        Hi,
if I'm not mistaken, changing the .desktop filename is not a problem,
as long as all the appstream data is properly updated.


Thx for clarification. But in that case, this change should still originate from upstream to prevent different .destkop for e.g. Fedora and Flatpak.


Changing the
<id/> in the appstream data is a problem, as noted here [1]. Changing
the <id/> also makes trouble to the plugins/extensions, they need to be
updated; the app lost their reviews;


Where is the reviews data stored actually? Is there a chance to update/rename/merge the data? Because e.g. in case of Vim, there were used at least 3 different IDs:


1) gvim.destkop

2) org.vim.Vim

3) org.vim.Vim.destkop


(where I believe that G-S is eventually going to represent the last two as one [1])


Vít


[1] https://gitlab.gnome.org/GNOME/gnome-software/-/issues/2663


  basically anything what references
the app by its <id/> will stop working/be lost.

The app can have "<provides><id>old-id</id></provides>", or something
like that it is, but the apps consuming the appstream data may or may
not work with it properly. It won't help with the reviews, from my
point of view.
        Bye,
        Milan

[1] 
https://www.freedesktop.org/software/appstream/docs/sect-Metadata-Application.html#tag-id-desktopapp

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

-- 
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to