Differences between revisions 2 and 3
Revision 2 as of 2005-11-22 19:18:54
Size: 4352
Editor: ?FransPop
Revision 3 as of 2005-11-22 19:21:05
Size: 4477
Editor: ?FransPop
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

See also [open http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=cdebconf-gtk-udeb bug reports against cdebconf-gtk-udeb].

Overview of open issues and things to be done for the ["DebianInstallerGUI"].

See also [open http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=cdebconf-gtk-udeb bug reports against cdebconf-gtk-udeb].


There is currently one remaining issue that blocks including the graphical installer from being included in the main installer build infrastructure: udeb dependency resolution.

udeb dependency resolution

During a build, not all dependencies between udebs can be resolved if all udebs are taken from the official mirrors. The current workaround is to copy some udebs to "localudebs", but this is not acceptable for the main build infrastructure.

The problem occurs if some udebs depend on a normal library package (libfoo.deb) while other udebs depend on the corresponding udeb (libfoo.udeb).

There are two known solutions for this issue.

  1. Change dependencies in udebs in such a way that they all depend in the same manner. This is what currently happens for the main installer. Problem with this solution is that the udebs involved are not maintained by the d-i team. Also, this would be ignoring the structural problem.
  2. Fix the toolchain (mainly dpkg-dev) to improve automatic dependency determination when udebs are build. A patch for this has been proposed but has not yet been implemented.

Other issues

  • Frontend crashes when user switches to a different virtual console while the frontend is busy. If the frontend is waiting for input, console switching works.
  • Option in the main menu to exit to a shell does not work.



The graphical version of the installer is currently available for Intel x86, AMD64 and PowerPC. The PowerPC port probably needs work to get different types of system correctly supported. Other architectures the graphical installer could be ported to include Sparc, Alpha and HPPA.


One of the main advantages of the graphical version of the installer is that it can support languages that use combining characters. We are currently using mainly TTF fonts, with the exception of Japanese and Chinese.

Fontconfig is used for font management. fc-cache files are automatically generated at startup.

The following issues are open with respect to fonts:

  • Not all fonts needed for the graphical installer have yet been packaged into udebs (needed for inclusion in the official Etch release).
  • Translators should check if their languages are displayed correctly and check for missing characters. Special attention should be given to Indic languages, Arabic and Hebrew.
  • There are known problems for Indic languages and Arabic. These need to be specified and traced. Possibly extra software is needed for correct display.
  • Ideal would be to have each character we need present in only one font. The current fonts have a lot of overlap which wastes space.
  • Possibly font configuration can be improved. It would be very nice if we could influence which font is used for a specific language.

Requirements for packaging fonts

  • Total amount of space used for fonts should be minimized.
  • Only font files that are actually used in the installer should be included.
  • Minimize overlap between fonts. Is is possible to "strip" characters from a font?

Overview of fonts currently used



  • Resolution
    • Currently fixed at 800x600. Should be made flexible (adapt to resolution set by system or user).
    • Interface should adapt itself so that text blocks are never too wide for optimal readability.
  • Improve accessability (for the visually handicapped). One way to do this is to support different themes (color schemes). (Note: should not lead to a major increase in initrd size.)
  • Progress bar in separate window.
  • Alternative (graphical) ways to start a shell or browse log files.
  • Interface design.
  • Create custom plug-ins for cdebconf to improve handling of some dialogs and make optimal use of possibilities offered by the graphical environment.

Reduce size of initrds

The initrds are currently very large which also results in fairly high memory requirements to run the graphical installer. Size has thus far not been a major concern, our focus has been on getting things working.

Options to reduce initrd size.

  • Library reduction for graphical libraries.
  • Remove unused files from udebs.
  • Reduction of space used by fonts (see above).