packagekit/TODO

69 lines
2.2 KiB
Plaintext
Raw Normal View History

2007-08-20 10:19:09 -07:00
Order of no particular importance:
2007-09-07 10:09:40 -07:00
*** Add a queing API ***
Jobs need to be queued so that read only jobs can be done in parallel,
but write jobs are done in serial. Maybe spawn each task and put it into a
paused state?
2007-09-07 12:37:37 -07:00
NOTE: RELEASE BLOCKER
*** Write some XML documentation ***
The backends/README file is woefully inadaquate for backend writers or even
people who just want to know how PK works.
NOTE: RELEASE BLOCKER
2007-09-07 10:09:40 -07:00
*** Add a way to import GPG keys ***
In fedora, if you add a signed repo you have to agree to the GPG key.
*** Split up PolicyKit install into different types ***
Have different permissions for signed and unsigned repos.
*** Add files in package into Description signal ***
We need a way to get the installed files into the UI.
*** Add package size into description signal ***
We need a way to work out how long something is going to take, and
to expose in the UI.
*** Valgrind everything ***
We leak memory like there is no tommorrow.
*** Add GetPercentage and GetSubPercentage for coldplugging ***
We need this for the PkWatch code.
*** task_client has to return GError ***
Client programs using libpackagekit should know the error, rather than just
"it failed"
*** Add logging so we can see what was installed/removed and when ***
Depends on transaction_id and sqlite integration.
*** Add "when installed" and "installed by" data into UI ***
Is this useful?
We would need to store package_id,installed_by,when_installed in a sqlite database
*** Add GetUpdateDetail
GetUpdateDetail(s=package_id)
UpdateDetail(
string url
string restart_enum
string updates
string obsoletes
string update_text
}
2007-09-07 10:09:40 -07:00
*** Have to have an UpdatesChanged signal ***
For the icon to update after we've done a system upgrade
2007-09-07 12:37:37 -07:00
NOTE: RELEASE BLOCKER
2007-09-07 10:09:40 -07:00
*** Dummy backend should use subpercent and install deps ***
It's not a great test case right now...
*** Handle rollbacks for select backends ***
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
* use an new method to handle the rollbacks and pass it to the backend