[Bug 1749777] Re: Syntax tweaks for snap-friendly output

Nish Aravamudan nish.aravamudan at canonical.com
Tue Feb 27 20:49:20 UTC 2018


I think it is an UX regression to go from:

$ sl
The program 'sl' is currently not installed. You can install it by typing:
sudo apt install sl

to (hypothetically):

$ sl
The command 'sl' can be installed as:
 snap sl
 deb sl

Because in fact neither of those are correct commands to install 'sl' :)

Why was this done this way?

Please minimally for the apt packages, use the same verbage (which users
are comfortable with and can c&p) as the previous c-n-f implementation.

Also, why can the snap packages not be provided with a similar `snap
install...` output (with sudo or not, as appropriate, I guess).

If a user does not know what a snap is, they are not given sufficient
information from the c-n-f output to know what to do with the
information now, which should be (IMO) consider a UX regression. And if
something is both a snap and deb, they now are not given c&p commands to
run.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to command-not-found in Ubuntu.
https://bugs.launchpad.net/bugs/1749777

Title:
  Syntax tweaks for snap-friendly output

Status in command-not-found:
  In Progress
Status in command-not-found package in Ubuntu:
  In Progress

Bug description:
  Would it be possible to change 'found' to 'installed', and show
  potential versions? For example:

  $ aws
  The program 'aws' can be installed as:
   * snap 'aws-cli' (1.14.38) 
   * deb 'awscli' (1.14.36-1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/command-not-found/+bug/1749777/+subscriptions



More information about the foundations-bugs mailing list