warn if common-id wasn't parsed
Bug #1814902 reported by
Harald Sitter
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snapcraft |
Fix Released
|
Medium
|
Claudio Matsuoka |
Bug Description
Currently you can apparently put anything in the common-id entry of an app. It'd be grand if snapcraft would get angry about common-ids it doesn't think are right.
For example to avoid typos:
```
apps:
kbruch:
command: kbruch
common-id: org.ked.
parts:
kbruch:
plugin: cmake
source: parse-info: [usr/share/
```
Also for appstream specifically the id is encoded in the xml. If it gets changed there but one forgets to also update the snapcraft.yaml, things would silently break and it'd not at all be obvious why on the snapcraft side of things.
tags: | added: 19.04 19.04-blue |
Changed in snapcraft: | |
assignee: | nobody → Claudio Matsuoka (cmatsuoka) |
status: | New → In Progress |
Changed in snapcraft: | |
status: | In Progress → Fix Committed |
milestone: | none → 3.5 |
importance: | Undecided → Medium |
Changed in snapcraft: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Is the encoding of common-id in the xml file name a KDE-specific policy? The Appstream specification requires the filename to be unique, but apparently doesn't set specific rules for naming the file.