-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Setup isn't unattended #7067
Comments
Packages are free to do whatever when compiling, there's not much we can do to guarantee an automatic installation. |
Couldn't we disable all confirmations for setup and then enable them after? On Sep 8, 2016 9:41 AM, "Eivind Fonn" notifications@github.com wrote:
|
We could advise |
To paraphrase Simon Peyton Jones, what if a package asks (when (y-or-n-p "Launch the missiles?")
(launch-missiles)) and we have advised |
@TheBB you are fast. Commenting from the future 😄 Anyway I agree with you. And just advising |
I didn't know there were packages that needed sudo. I suppose there isn't a sane way to handle this. I wonder if advising yes-or-no-p in cases except the sudo one you mention is possible though. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid! |
Setup requires user to confirm our is okay to kill buffers so you can't just run setup and go do something else.
The text was updated successfully, but these errors were encountered: