Debian Codegraph @

doc/TODO

raw
1 General:
2 * The ConfModule should not return the backup return code, ever, if
3 the confmodule it talks to has not indicated it has that capability.
4 * Get rid of the horrendous fd #3 hack in /usr/share/debconf/confmodule.
5 Unfortuantly, many packages probably depend on the hack. Options are to
6 find all such packages (by examining/auditing all packages that use
7 debconf), to come up with a new shell interface that is so much cooler
8 people will want to migrate to it, and make it not use the hack,
9 or to decide with Wichert that debconf should not ursurp stdin/out.
10 * Should be able to jump to debconf config when debconf is interacting with
11 the user.
12 * Regression tests.
13 * I need to implement the container template type. That's gonna be fun..
14 * Something I see frequently is a select list that needs lots of explination
15 for each option. It'd be neat if the explination could be added as a
16 parallell list with the select list, to keep the actual tokens that the
17 confmodule script gets back short. See modconf for how such a list could
18 display in whiptail.
19 * Darxus <[email protected]>
20 > I will probably leave debconf set to ask me every question for quite some
21 > time. But it would be nice, in addition the "yes" & "no" buttons, to have
22 > a "don't ask me again" checkbox, so next time it'll just used the stored
23 > answer.
24 Dialog frontend couldn't support this, but the rest could.
25 * Add a dbdriver format module that understands debconf-show output;
26 then you can pipe that into a ssh to a remote host and use
27 DEBCONF_DB_OVERIDE and fun stuff like that.
28
29 Protocol and spec revisions:
30
31 * Expose a way to iterate over questions; this would allow a UI independant
32 database browser to be easily written.
33 * Document the behavior of the seen flag when backing up in the same config
34 script run. (Tausq?)
35 * Get rid of notes, that data type is too prone to abuse; error is better.
36
37 Database:
38 * The division between Debconf::Config and Debconf::Db still needs thought.
39 They both call each other, but worse, Debconf::Db->load needs to be
40 called in dpkg-preconfigure and others before Debconf::Config->blah can
41 be used, which is unintuitive.
42 * There's also the Force-Flag-Seen thing, which is really a more generic
43 forcing of any given flag to any vale, and should expand to forcing any
44 field to a value too, I'd think. Perhaps it should be an overlaid
45 database really? Yes, I think so..
46 * Regression tests!
47 * The Backup driver cannot deal with situations where the db already has
48 stuff and the copy does not. Perhaps it should copy items whole from db
49 to copy if they do not already exist in the copy and an operation is done
50 to them?
51 * Debconf does not try to deal with things that were not passwords becoming
52 passwords. They stay in config.dat, world-readable. I'm not sure it _can_
53 detect this and move them to passwords.dat.
54 * PackageDir dbdriver needs testing, and needs to become used by default..
55 * Hmm, as a slight mod to PackageDir, it just might be possible to use
56 /var/lib/dpkg/info/*.templates as a packagedir database. The 822 module
57 does not currently handle the word-wrapped descriptions in there, and
58 it'd sorta have to be read-only and stacked under another db or something
59 to record owner info though. The overlying db would need to get copies of
60 templates if they got 2 owners, so the package they're in doesn't leave
61 the other owner stranded. Still, this would easily save 1 mb on most
62 debian installs, so I really should pursue it.
63
64 Noninteractive frontend:
65 * Just because it's noninteractive doesn't mean it can't output to the
66 console. I think it should do so, at least for errors (in addition to
67 mailing them). That way if an error is displayed and the package install
68 fails you don't just see it dying, you immediately see why.
69
70 Readline frontend:
71 * It might be better in terse mode to not print out the list of choices for
72 a select list, and instead rely on them using tab completion. However,
73 for this to be usable, it would need to ditch the numbered shortcuts in
74 this case, neither listing them in tab completion nor making them show up
75 as defaults in the prompt.
76
77 Dialog frontend:
78 * It'd be nice if the Dialog stuff could catch text that was to be
79 displayed that is in the same block, buffer it, and display it up at the top
80 when it prompts for an input that is in the same block.
81
82 Gnome frontend:
83 * Make it use a multiselect box instead of all the check boxes
84 * Add support for blocks and containers, both of which should let multiple
85 questions be grouped together in nice ways on the screen.
86 * It seems that text elements hang around on each page displayed after the
87 one they should be on. Actually, the Elements are not hanging around, but
88 the gtk label widgets are, and I don't know why.
89
90 Kde frontend:
91 * Improve error handling when debconf-kde-helper terminates unexpectedly.
92
93 Web based frontend:
94 * Well, a little security would be nice! It only allows connections
95 from localhost, but even that isn't good enough at all.
96 * Passwords are completly insecure.
97 * It can support blocks, so add them. I guess they could be used for
98 arranging questions into tables or something.
99 * It should have a config screen. In it, you configure the frontend itself.
100 One option would be to make it be in "quiet" mode -- this would make it
101 not display extended descriptions, just provide links them. Another thing
102 to configure would be what priority of questions it is displaying.