-
Notifications
You must be signed in to change notification settings - Fork 233
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
[feature request] Ask before updating #225
Comments
@Firesphere I'm not the developer of this, but I don't see the usage of this. Why would you run the rpi-update if you are not interested in doing an update? |
It doesn't need to be the question. But at least inform the user before going forward. Same as I would be interested in it, as, for example, the latest update I ran, I noticed a notice saying "this will bump the kernel to 4.4.x, which might cause problems" |
Hmmm, I don't quite agree with your comparison. apt-get upgrade goes for all packages. You should only execute rpi-update if you really want to update the firmware and you know what you are doing. That is the same if you really want to update the firmware on your PC. The notice about bumping to kernel 4.4.x has been there a really long time, I think it is a year or something like that. IMHO no ordinary user should use the rpi-update, just like no ordinary user should upgrade firmware on PC. |
Xref: #201 |
I disagree with that, as rpi-update is even advertised on multiple websites, as the go-to way to upgrade your kernel. There are a lot of people, who blindly follow a website like Lifehacker or whoever is an authority and run rpi-upgrade without knowing the implications. |
As I said I'm not the developer, so it is not my decisions. The Xref is to a PR similar to this and that hasn't been merged... |
See the README on:
Many updates here don't bump the kernel version, so a message like:
doesn't make sense. |
The first line of the README is rather misleading, and even to this day I see people who don't understand what rpi-update is, running it in order to get updates for their Pi. If this statement was true in the past, it certainly isn't anymore.
I spent a lot of effort actively warning people against rpi-update and encouraging websites to remove references to it as the canonical source of updates. This was to stem a tide of support requests from people who had basically broken their Raspbian install with pre-release firmware/kernel releases and couldn't get anything to work. I think there's a rift between the people actually experienced enough to use this utility, and the people who have to deal with the fallout from it being used unwittingly and adding a warning would certainly help to close that gap. That said, the problem is pretty minimal these days, but I'd wholly encourage attention to this Issue and the PR linked because it could save someone a real headache in the future. |
@Ruffio (since I know you're not the developer; but to whom to report to?) |
@popcornmix is the developer. Im just a uset like you... |
|
I noticed that the bump to 4.14 branch requires YN confirmation to proceed which is fine but I'd propose either an env var or a -y param (similar to apt-get) to support expert, non-interactive installs. |
@moodeaudio see #275 |
@Firesphere can this be closed? |
Yes, as I think it's actually been implemented exactly the way I intended, a small confirmation system, that tells you what's gonna happen. I agree with @moodeaudio , that a Very much cheers and have a great holiday/christmas/new year/etc. :) |
When updating, it would be nice if the updater said something like
So as a user, I know what is going to happen if I say yes.
The text was updated successfully, but these errors were encountered: