parse-info-all bool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snapcraft |
New
|
Undecided
|
Unassigned |
Bug Description
It would be cool if parts had a `parse-info-all` key which enables parsing all data it can find.
Currently a developer needs to list all appstream files AND then also set the common-id on the app. This seems excessive. Since appstream files have well known locations it'd be far easier to simply enable extracting all meta data from a part.
So
```
name: sampleapp-name
adopt-info: sampleapp
apps:
sampleapp:
command: sampleapp
common-id: com.example.
otherapp:
command: otherapp
common-id: com.example.
thirdapp:
command: sampleapp
common-id: com.example.
parts:
sampleapp:
plugin: dump
source: http://
parse-info: [usr/share/
```
to
```
name: sampleapp-name
adopt-info: sampleapp
apps:
sampleapp:
command: sampleapp
common-id: com.example.
otherapp:
command: otherapp
common-id: com.example.
thirdapp:
command: sampleapp
common-id: com.example.
parts:
sampleapp:
plugin: dump
source: http://
parse-info-all: true
```
If full extraction isn't viable for a given piece of software the developer may still opt to do the explicit list, so nothing is lost. In the event auto extraction will be the desired thing (which to me seems to be case for probably just about all FLOSS desktop application) the explicit listing is entirely superfluous.
tags: | added: 19.04 19.04-blue 19.04-external |
Changed in snapcraft: | |
status: | Expired → New |
How would we select which description and summary, at the least, to use from those discovered appstream files?
Also, I would suggest to change this if implemented to "parse- info-appstream- all: true" or to "parse-info-all: appstream" since parse-info is pluggable and can parse other forms of metadata.