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

See also open [http://bugs.debian.org/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 (see also [http://lists.debian.org/debian-boot/2005/10/msg00955.html this thread]).

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 [http://lists.debian.org/debian-dpkg/2005/06/msg00198.html patch] for this has been proposed but has not yet been implemented.

Other issues



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:

Requirements for packaging fonts

Overview of fonts currently used

Note This is just an initial collection we've put together. There are known issues for some languages and possibly additional fonts are needed. It also is very much possible this is not the optimal mix of fonts for the graphical installer.


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.

Migrate from gtk+-directfb-2.0.9 to gtk+-directfb-2.8.3

The udebs for gtk+-directfb are based on a [http://www.directfb.org/downloads/Libs/gtk+-directfb-2.0.9-2.tar.gz set of sources] released in Apr 2003; it's now possible to build a set of libraries based on gtk+2.8.3 which was released around Oct 2005. The main problem is that [http://wiki.debian.org/DebianInstallerGUIBuild building] is rather tricky, and there are no pre-patched sources available from upstream. Upstream author is now working on including directfb backend into Cairo main line as a first step; inclusion of gdk-directfb code into gtk+ tree should follow then. udebs could be then easily created.