How will PackageKit handle installation an application that needs user interaction?
Upgrading, installing or removing packages has to be 100% silent. The user cannot be prompted mid-transaction for questions as these will not be handled in PackageKit. The backend should do the right thing, as these questions mean very little to the average user. The reasons for this are as follows: • The messages cannot be translated as the daemon is running in the C locale, and there may be multiple running session clients in different locales. • Stopping the transaction and waiting for input would also mean the methods are no longer “fire and forget”. • Security updates can now be performed automatically, i.e. when the user is idle. There’s no user at the console in this case to answer questions. • Due to the client/server split of PackageKit, a non-root user would be able to change the answer of debconf scripts, and another PolicyKit role would have to be defined. In this case a situation could arise where a user is able to update software, but not agree to EULAs, thus making the t
Related Questions
- I want to use a user account for the Application Pool. Does this account needs to have administrative rights on the Web Front End (WFE) server?
- How do I configure a silent installation to an agent without user interaction or intervention?
- How can I perform a (mass-)installation without user interaction (aka "unattended setup")?
