Evolinx/packagekit
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update TODO

Browse Source
This commit is contained in:
Richard Hughes 2007-09-19 23:28:50 +01:00
parent 8955d94956
commit 5fab68022a
1 changed files with 6 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
TODO
View File

@ -1,12 +1,9 @@
Order of no particular importance: Order of no particular importance:
*** API Changes *** *** API Changes ***
s/GetJobList/GetActiveTransactions s/GetJobList/GetTransactions
s/JobListChanged/ActiveTransactionsChanged s/JobListChanged/TransactionListChanged
s/PkTask/PkBackend (and local variables) s/GetOldTransactions/GetTransactionDetails
*** Put the pk-application taskbar in the status section ***
It looks wrong where it is...
*** Have to have an UpdatesChanged signal *** *** Have to have an UpdatesChanged signal ***
For the icon to update after we've done a system upgrade For the icon to update after we've done a system upgrade
@ -36,21 +33,18 @@ Need to convert the role to an enum
Client programs using libpackagekit should know the error, rather than just Client programs using libpackagekit should know the error, rather than just
"it failed" "it failed"
*** Add logging so we can see what was installed/removed and when *** *** Log what was installed/removed and when ***
Depends on transaction_id and sqlite integration. Need to monitor the Package's emitted by the task and encoded to a string
*** Add "when installed" and "installed by" data into UI *** *** Add "when installed" and "installed by" data into UI ***
Is this useful? Is this useful?
We would need to store package_id,installed_by,when_installed in a sqlite database We would need to store package_id,installed_by,when_installed in a sqlite database
*** Dummy backend should use subpercent and install deps *** *** Dummy backend should use subpercent and install deps ***
It's not a great test case right now... It's not a great test case right now...
*** Handle rollbacks for select backends *** *** Handle rollbacks for select backends ***
To do rollbacks sanely in PK we need a few things: To do rollbacks sanely in PK we need a few things:
* convert the job into a transaction_id
* save the transaction_id's and descriptions to a database
* add a method to get the transaction_id's in the last x transactions
* write an application that can see the description of the transactions * write an application that can see the description of the transactions
* use an new method to handle the rollbacks and pass it to the backend * use an new method to handle the rollbacks and pass it to the backend