-
-
Notifications
You must be signed in to change notification settings - Fork 437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
snap v0.16.0 / Implement Note of Discontinuation #804
Comments
Note that this issue is especially important, since Ubuntu's
|
Semnodime
added a commit
to Semnodime/lsd
that referenced
this issue
Jan 18, 2023
This was referenced Jan 18, 2023
zwpaper
pushed a commit
that referenced
this issue
Jan 18, 2023
(Moved to #1089, apologies for the annoyances.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
lsd --version
:lsd 0.16.0
(snap
latest/stable
,0.16.0
2019-08-02
wg6vD3jHxl87UtHKsX9obkJMYCed1JX3
)Expected behavior
The snap version of
lsd
should inform user of limitations (see #79) and current state of of being discontinued (also see #79).Actual behavior
Currently, users have to individually notice the dysfunctionality of current snap lsd version (
wg6vD3jHxl87UtHKsX9obkJMYCed1JX3
), search for the known issue to be able to rule out self-inflicted system misconfiguration, therefore have the burden of finding the closed issue regarding discontinuation of the snap version as decided by @Peltoche imposed on them.This leads to a bad UX for new users, especially when honoring the above path of collaboration as opposed to least effort (posting a new issue or leaving the project altogether).
I hereby want to inform about the necessity to update the snap affair and suggest leaving a note for users that their installation has been discontinued and known game-breaking bugs (unless (at least as configured currently) installed via
--devmode
which implies--dangerous
and thus potentially unverified signatures).To my mind come the following solutions (No great care has been taken to evaluate whether they are promising solutions in particular):
--devmode
The text was updated successfully, but these errors were encountered: