Except that in this case, his real question "how do I ask something from the user when installing a module" still hasn't been answered - everyone is focussing on an irrelevant detail.
Also, I didn't suggest to him to ask a more detailed question. I just suggested to him to change some details to not trigger responses that don't help him to answer his question. | [reply] |
no one is focusing on irrelevant detail -- everyone is focusing on the right answer, that is: "you shouldn't do that".
kind of like: "How do I aim for my toe with a .38 revolver?" -- "you shouldn't do that, here is a pair of nail-trim scissors".
[]s, HTH, Massa (κς,πμ,πλ)
| [reply] |
Howdy!
"Don't do that" is *not* the unitary "right" answer. There exist a range of circumstances
where it is appropriate and/or necessary to interact with the user during the installation
process in order to properly build the module. It may be that the input can be scripted
or put in a configuration file, but it's not always appropriate to insist that the user
create that from whole cloth up front.
Fortunately, answers that speak to the question have been offered.
| [reply] |
Why didn't you answer it?
| [reply] |