Opened 12 years ago
Closed 12 years ago
#29 closed defect (invalid)
Improve State for core packages
| Reported by: | Iritscen | Owned by: | Christian |
|---|---|---|---|
| Priority: | trivial | Component: | AEI2/UI |
| Keywords: | Cc: |
Description
As seen in http://wiki.oni2.net/File:AEI_core_window.jpg, core "Tool" packages end up with the status __D when they ought to be I_D. Some suggestions:
- The simplest solution is to remove the State column altogether, as there's nothing the user can do about the state of these packages anyway :-)
- Then again, perhaps with the new checksum verification feature, it will be easier to confirm that "Tools" are installed.
- The State column could even be slightly re-purposed so that when a change to an installed "Tool" is detected, it triggers the _U_ flag, or else, to avoid confusion, this State column can show a different flag like _M_ for locally-modified files.
Note:
See TracTickets
for help on using tickets.
The core tool packages already get the I flag if they get installed. The problem is that with the change in state saving I did for #5 and #14 the old information about installed core tools was lost though they still won't get installed again until there's an update to their files on the Depot. Or until you delete the package folders locally ;)