The difference between snap name and store package name is not obvious
Bug #1914233 reported by
Sebastien Bacher
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
Creating a snap from a git repository, the +new-snap page starts by asking a name, described as 'The name of the snap package'. The description is not really clear on what the name represent exactly and how it's different from the store package name.
I was setting up a thunberbird beta build from a specific git branch and my first reaction was to enter 'thunderbird' as the snap name since that's the name of the project and from the generated snap, which errored out since the name was already used.
Would it be easier to understand if the description was 'The name of the snap build recipe being created' or something similar?
Related branches
~twom/launchpad:better-text-for-snap
- Colin Watson (community): Approve
-
Diff: 16 lines (+2/-2)1 file modifiedlib/lp/snappy/interfaces/snap.py (+2/-2)
| description: | updated |
Revision history for this message
| Colin Watson (cjwatson) wrote | #1 |
| tags: | added: confusing-ui lp-snappy |
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
Revision history for this message
| Sebastien Bacher (seb128) wrote | #2 |
| Changed in launchpad: | |
| status: | Triaged → Fix Committed |
| summary: |
- The different between snap name and store package name is not obvious + The difference between snap name and store package name is not obvious |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Calling the recipe object a "snap" was a mistake in the initial design of this feature. We've been moving towards calling it "snap recipe", though mostly only colloquially so far. Would "Snap recipe name" be clear enough, do you think?