Aptdaemon already shows the name of the binary/application which holds the lock in the status message: "Waiting for XXX to exit...". Possible values in real life are aptitude, apt-get, dpkg and synaptic.
The status of the transaction is set to PK_STATUS_ENUM_WAITING_FOR_LOCK on the PackageKit interface and to aptdaemon.enums.STATUS_WATING_FOR_LOCK on the aptdaemon interface which is used by s-c.
So basically all technical requirements are there.
An important use case is the daily update of the cache to check for upgrades. It "currently" doesn't use aptdaemon but calls apt-get update. So you can get random cache locks.
Aptdaemon already shows the name of the binary/application which holds the lock in the status message: "Waiting for XXX to exit...". Possible values in real life are aptitude, apt-get, dpkg and synaptic.
The status of the transaction is set to PK_STATUS_ ENUM_WAITING_ FOR_LOCK on the PackageKit interface and to aptdaemon. enums.STATUS_ WATING_ FOR_LOCK on the aptdaemon interface which is used by s-c.
So basically all technical requirements are there.
An important use case is the daily update of the cache to check for upgrades. It "currently" doesn't use aptdaemon but calls apt-get update. So you can get random cache locks.