-
Notifications
You must be signed in to change notification settings - Fork 160
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
Only do package update, no system upgrade #178
base: main
Are you sure you want to change the base?
Conversation
The guides already say to to an upgrade before even running this script and the way this works right now it just hangs for a long time without any feedback for sometimes 10-20 minutes. This is I think not a very good UX. See this issue on more reasoning: adafruit#174 The default nature of upgrading all the system packages is I think a bit too many changes than one would expect from installing a python package.
The reason we have the upgrade is so we can have users having issues run the script to make sure they are up to date. I think we could add a parameter to skip the upgrade step. Would that be an acceptable compromise? |
I think without feedback of the process I would not have it in there. On the weekend I ran it on a fresh Pi and apparently there was some error in the process and it was just stuck forever but you never really know. If you think its really necessary to upgrade the whole system and not just the relevant packages I would have it ask during the process if you want to upgrade or not and if possible forward the output of apt to the user so they see what is going on and have them confirm individual things. At the moment it would just wipe all config changes a user may have made because of the -y option. Otherwise I would maybe put in a notice but leave out the system upgrade for the user to run manually. |
Ok, yeah. Asking in the process is another great option. |
I updated the code to ask to update the packages rather than foregoing them altogether. |
definitely better but can |
Kind of going through some of these that have been sitting awhile. regarding your last comment, adding stdin to python_shell is a great idea. I think it currently only does stdout and stderr. However, this might take some experimenting so it stays in order. |
I just released a new version of python_shell and have fixed the run_command. Forwarding stdin wasn't necessary, but it now works interactively and doesn't lock up. |
The guides already say to to an upgrade before even running this script and the way this works right now it just hangs for a long time without any feedback for sometimes 10-20 minutes.
This is I think not a very good UX. See this issue on more reasoning: #174
The default nature of upgrading all the system packages is I think a bit too many changes than one would expect from installing a python package.