Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is the <releases/> tag really required? #113

Closed
elvisangelaccio opened this issue May 12, 2017 · 2 comments
Closed

Is the <releases/> tag really required? #113

elvisangelaccio opened this issue May 12, 2017 · 2 comments
Assignees

Comments

@elvisangelaccio
Copy link

From the spec:

⁠2.1.3. XML Specification
The XML for a generic component definition starts with a tag as the root element. The element must at least have an id, name and releases tag

but appstreamcli validate does not complain if the releases tag is missing. In fact, the tag is not used at all in KDE applications. Bug in the spec or bug in the validator?

@hughsie
Copy link
Collaborator

hughsie commented May 12, 2017

Quite a few XFCE and GNOME apps use releases in the AppData, and for packaging formats like flatpak it's the only way we can get any kind of release notes.

@ximion
Copy link
Owner

ximion commented May 13, 2017

@elvisangelaccio This is actually a typo, the component must have an id, name and summary tag to be valid. I'll fix this tomorrow (and I should really invest a bit of time at some point to read the full specification again, to check for consistency - a lot of bits have changed in the past).
Regardless though, as @hughsie said, a releases tag is a useful thing if it is kept up to date, so you might as well add one :-)

@ximion ximion added the bug label May 13, 2017
@ximion ximion self-assigned this May 13, 2017
@ximion ximion closed this as completed in f07a2ae May 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants