Prevent interactive updaters, fail or skip, in that order depending on what is available.
Why?
Upstream autoupdaters can interrupt scripting and UX
What-should happen?
We should be able to skip any script (or all of bs) if a shell is interactive with this. If possible we should scope this to when they'd come up in commands that we would run. Namely in .*rc/.profile we should run as little as possible to prevent locking systems. Failing after you have a shell is fine, failing during initialization is bad.
This is both a very soft, but very important request that is difficult to fully test. Adding this repo to base alpine/ubuntu/debian/fedora with just running basic-setup.sh should not cause failures on restarting at a minimum. The goal is to do the minimum during init and cause failures during run if there are issues for more full logs for interactive users, because this is designed for desktops more than servers.
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Contact Details
mrlunchbox777@gmail.com
Feature Description
Prevent interactive updaters, fail or skip, in that order depending on what is available.
Why?
Upstream autoupdaters can interrupt scripting and UX
What-should happen?
We should be able to skip any script (or all of bs) if a shell is interactive with this. If possible we should scope this to when they'd come up in commands that we would run. Namely in .*rc/.profile we should run as little as possible to prevent locking systems. Failing after you have a shell is fine, failing during initialization is bad.
Covers this TODO
Steps to Test
This is both a very soft, but very important request that is difficult to fully test. Adding this repo to base alpine/ubuntu/debian/fedora with just running
basic-setup.shshould not cause failures on restarting at a minimum. The goal is to do the minimum during init and cause failures during run if there are issues for more full logs for interactive users, because this is designed for desktops more than servers.Code of Conduct