Jump to conversation
Unresolved conversations (5)
@ximion ximion Jun 12, 2017
Make that "service" a `<literal>service</literal>`
docs/sources/metainfo/service.xml
mvollmer
@ximion ximion Jun 12, 2017
Should it? And if so, what does the `service` provided-item contain as value?
Outdated
docs/sources/metainfo/service.xml
mvollmer
@ximion ximion Jun 12, 2017
Don't say "file" as AppStream metadata might not be retrieved as file, and this generally is a bit confusing. Usually, we use "component" here. Additionally, I try to avoid using the term "document" to refer to the text people are reading, because since there are XML documents and YAML documents as well as two types of AppStream "documents" this is confusing. So, I'd probably have written something like "The component described here is built upon...."
Outdated
docs/sources/metainfo/service.xml
mvollmer ximion
@ximion ximion Jun 12, 2017
Duplicate text here.
Outdated
docs/sources/metainfo/service.xml
mvollmer
@ximion ximion Jun 12, 2017
Nitpick: One excessive space here... What does "manage" mean? Do you mean start? Do you mean start/restart/stop? What happens when the service is a "oneshot" unit? Maybe clarify that.
Outdated
docs/sources/metainfo/component.xml
mvollmer ximion
Resolved conversations (0)