$ 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.
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.