Some packages get installed that require some sort of post configuration to get working. Each having a different way to configure it. I think it would be very beneficial if a package could provide an XML file or some sort of bundle of information along with the package to get handed off to PackageKit to allow for Post configuration.
Here are a couple of examples:
You install freeipa. The user must know that they need to run ipa-server-install or ipa-client-install. In this case the packager or developer of freeipa could create a meta file which could be as simple as
providing information that the user has 2 choices client or server. If they select client it opens a terminal and kicks off ipa-client-install, etc. Or if they wanted to make it more user friendly they could provide information to build an interface to collect the information from the user and process it accordingly.
You install Gallery2. Here the user must have Apache and Mysql running, and a database and user created for installation. Here the packager or developer could provide information about dependencies. Then again the pacakger could just have it kick off firefox pointing to the installation page or provide the information to create a configuration interface.
This isn't a problem with PackageKit but it is an overall problem that PackageKit or a sister project could solve.
In Debian/Ubuntu this cases are handled by debconf which allows to configure the package at installation time (and afterwards) and to display important notifications.
So I would favor not defining a new method based on xml, but to put this into the backends.
We moved the upstream bugtracker to GitHub a long time ago. If this issue still affects you please re-create the issue here: https://github.com/hughsie/PackageKit/issues
Sorry for the impersonal message, and fingers crossed your issue no longer happens. Thanks.