summaryrefslogtreecommitdiffstats
path: root/TODO
blob: 120224b8278287fcb23174ed434de6e1e5c1168e (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
$Id$
Things to do on mdkonline
-------------------------------------------------------------------------------

 * whole package:
   force package update if available, before any other update,
   then restart update process (mdkapplet/mdkupdate)

 * mdkapplet:
   several releases of the same package may be installed along each other
   (seen for libaspell15, ~december); check that at least the most up to
   date available package is installed.
   Should it be handled by rpm instead?

 * mdkonline, mdkupdate:
   add animated fluffy tux for waiting during computations?

 * mdkapplet:
   a launch system menu item should appear in System > ?

 * mdkapplet:
   should appear only for notification (no config, config problem, available
   updates), not when everything is fine?

 * mdkapplet:
   when minimizing applet, minimize to icon, not to task bar

 * mdkapplet:
   applet popup display the number of available updates (requires full diff
   check, changes silentCheck() )

 * mdkupdate:
   at start, first query the server to check if anything should be done;
   if nothing, don't run urpmi, just upload the config.
   if not in command-line mode, an alert box should inform that no update
   is available.

 * mdkupdate:
   should exit, if another mdkupdate is running (done),
   or if the urpmi db is locked.

 * mdkupdate:
   - started every 2 hours +/- salt ?
   - should compare system mandrake-release with the one on the server to detect if system was updated without starting mdkonline wizard.

 * mdkupdate --auto 
   when failing, informative feedback should be displayed (not authenticated,
   not subscribed, not activated, st like that) (command line)

 * mdkupdate --auto
   MAILTO to the email of the user instead of root.
   output the system name and account name.

 * for pro version (v2)
   changer server/client protocol:
     - move to SOAP or REST,
     - client queries server for higher-level tasks (from a predefined list)
       (package update, install, uninstall, config setting, data processing)


 * move authentication calls to new customer db (remove expert/online calls
   for that purpose).


-------------------------------------------------------------------------------
$Id$