← Back to issue list

Get Desktop icon from snap instead of source tree

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1995856
Type
issue
State
open
Author
~merlijn-sebrechts
Labels
—
Created
Updated
Closed
—

Current evaluation

No syntax supports sourcing the top-level icon from a built part; implementation is needed for downloaded build-time assets, but the issue has no maintainer triage or discussion.

Suggested action: needs triage

Reason: The request is valid and clearly identifies the build-time ordering problem, but it remains unassessed: there are no labels, maintainer comments, proposed syntax, or acceptance criteria. Supporting a part-qualified path and resolving its payload only after parts are built adds packaging and validation complexity.

Evaluated by: mr-cal-bot

Impact: 45 Quick Win: 12 Complexity: 65 Confidence: 82 Actionability: 78

Issue body

Given many snaps download files at build time, the icon might not be available in the source tree. The `icon` field in snapcraft.yaml should have a way to specify a path to a file in the snap itself, instead of the source tree.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 45
Quick Win: 12
Complexity: 65
Confidence: 82
Actionability: 78
needs triage No syntax supports sourcing the top-level icon from a built part; implementation is needed for downloaded build-time assets, but the issue has no maintainer triage or discussion.
stealth/space-bunny-alpha
Impact: 32
Quick Win: 21
Complexity: 28
Confidence: 97
Actionability: 93
close resolved Requests that icon paths reference build-generated files in the prime tree; prime-relative icon resolution is now implemented for both legacy and mediated packaging.
qwen3.6-35b-a3b-mtp-q6
Impact: 10
Quick Win: 8
Staleness: 100
Complexity: 20
Confidence: 70
Support Request: 10
close not a bug Feature request to allow icon field in snapcraft.yaml to reference files in the snap instead of source tree. Issue is 3.8 years old with no maintainer interaction.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 30
Confidence: 85
Support Request: 10
close stale Request to let snapcraft.yaml icon field reference files inside the built snap instead of the source tree. Open for 3.7 years with zero comments or maintainer engagement.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 40
Confidence: 85
Support Request: 10
close stale Feature request to allow snapcraft.yaml icon field to reference files inside the built snap package rather than the source tree. Unaddressed for over 3 years with no maintainer interaction.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 30
Confidence: 80
Support Request: 10
needs triage Feature request to allow snapcraft.yaml icon field to reference files within the built snap rather than the source tree. Unlabelled and inactive for over 3.7 years with no maintainer response.

Update history

Date Change
created

Related issues

No related issues found above the similarity threshold.