On Friday, January 17, 2025 1:46:20 PM MST Phil Wyett wrote: > On Fri, 2025-01-17 at 13:37 -0700, Soren Stoutner wrote: > > On Friday, January 17, 2025 12:26:52 PM MST Phil Wyett wrote: > > > On Fri, 2025-01-17 at 11:42 -0700, Soren Stoutner wrote: > > > > On Friday, January 17, 2025 10:03:21 AM MST Soren Stoutner wrote: > > > > > Appsream file name: Use reverse domain name notation appended by > > > > > .appdata.xml. ID: Use the same reverse domain name notation. > > > > > > > > A review of the documentation taught me that .appdata.xml is deprecated > > > > (but > > > > > > it will still work) and the recommended suffix is now .metainfo.xml. > > > > > > > > https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#s > > > > pec > > > > -> > component-location > > > > > > Hi Soren, > > > > > > IN this case and for others reviewing the docs[1] and using the > > > specification > > > is best. I have done this with rednotebook over the years, though upstream > > > does not want rDNS naming. > > > > Where do you see that upstream does not want rDNS naming? They docs I am > > reading explicitly say it is required. > > > > “Upstream projects can ship one or more metainfo files in > > /usr/share/metainfo/% > > {id}.metainfo.xml, where id is a unique identifier of this specific > > component.” > > > > https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#spec-> > > > component-location > > > > “The ID must follow a reverse-DNS scheme, consisting of {tld}.{vendor}. > > {product}, for example org.kde.gwenview or com.hugski.colorhug2. Ownership > > of > > {vendor}.{tld} in the domain name system guarantees uniqueness of IDs.” > > > > https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-i > > d-generic > Soren, > > For rednotebook the application name is used for the ID and .desktop file. It > did previously did give a lintian warning until appstream in Debian went nuts, > but upstream is not willing to make all other associated changes. It is his > choice, so I am fine with it. > > It works fine. It may become a necessary in the future for upstream to make > the move, but until then I go with his wishes.
In my experience it isn’t that hard to modify the metainfo.xml and desktop files for Debian, either with patches or by creating custom files in the debian directory. Also, in my experience, upstream is usually pretty open to accepting submissions fixing these problems, although there are probably a few upstreams that aren’t. In any case, it isn’t that hard to bring these files into compliance with the AppStream protocol as documented in the freedesktop.org documentation I linked to above, so it seems like it is something worth doing. Other people may feel differently, but I personally like to address any of these problems before sponsoring a package. -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
