The difference between snap name and store package name is not obvious

Bug #1914233 reported by Sebastien Bacher on 2021-02-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
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

description: updated
Colin Watson (cjwatson) wrote :

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?

tags: added: confusing-ui lp-snappy
Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
Sebastien Bacher (seb128) wrote :

Thanks for the quick reply Colin, yes 'snap recipe name' is clear enough in my opinion :-)

Tom Wardill (twom) on 2021-02-03
Changed in launchpad:
status: Triaged → Fix Committed
Colin Watson (cjwatson) on 2021-02-08
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.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers