added some docs on issues with the progress bars
r2246
Martin Sjögren
21 years ago
0 | Issues with the cdebconf progress bars | |
1 | ====================================== | |
2 | ||
3 | The cdebconf progress bars are currently driven by the following protocol: | |
4 | ||
5 | PROGRESS START <min> <max> <title-template> | |
6 | PROGRESS STEP <inc> <info-template> | |
7 | PROGRESS STOP | |
8 | ||
9 | ||
10 | ||
11 | This is wildly incompatible with what debootstrap uses, which is: | |
12 | ||
13 | P: <curr> <max> <title-string> | |
14 | I: <info-string> | |
15 | ||
16 | In debootstrap there is no concept of starting and stopping, a progress | |
17 | bar simply "is" and has a current and a max value. The info is decoupled | |
18 | from the actual stepping. | |
19 | ||
20 | ||
21 | ||
22 | Thus, I suggest we change the protocol to something that interacts more | |
23 | easily with debootstrap, something like: | |
24 | ||
25 | PROGRESS START <min> <max> <title-template> | |
26 | PROGRESS SET <val> | |
27 | PROGRESS INFO <info-template> | |
28 | PROGRESS STOP | |
29 | ||
30 | The quick&dirty way would be to just overlay this, since there are no | |
31 | conflicts in naming, but that feels like a bad solution. I would rather rip | |
32 | out the current code before it gets too widely used. | |
33 | ||
34 | ||
35 | -Martin |