2 ms·
Any such configuration should be done separately. I could stand it being done in a pkg I would never install and which can only be depended on by other pkgs of
by cryptonector 9y ago
Any such configuration should be done separately. I could stand it being done in a pkg I would never install and which can only be depended on by other pkgs of this type (i.e., which configure but don't include artifacts except by depending on the pkgs that provide them).
It is beyond awful that what should be an unattended operation (install, upgrade an OS) isn't. It's completely unacceptable, and utterly intolerable.
Yes, I'm aware of "answer" files. That was SVR4's compromise: you'd put all interaction into one kind of script that can be run separately from the actual pkg installation and which produces "answers", and then you can furnish those answers at actual pkg installation time. But in practice most developers were not really aware of all of this. The cognitive load of SVR4 packaging was too high. Interaction and package scripting really complicates packaging. Please stop.
- Annatar 9y agoNone of my packages have ever been interactive, and they never needed any answer(4) files. I agree with you that packages should never be interactive, because at that point, automation is lost and one of the core capabilities of packaging defeated. Such things are usually done by inexperienced personnel who view packaging as a burden rather than as a strategic advantage and an extremely capable automation mechanism. I am none of those people.