Overview of open issues and things to be done for the ["DebianInstaller/GUI"].

See also open [ bug reports against cdebconf-gtk-udeb].



The main issues left are:

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 [ 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 [ 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 [ needs work] to get different types of system correctly supported. Other architectures the graphical installer could be ported to include Sparc, Alpha and HPPA.


For font information, please see ["DebianInstaller/GUIFonts"]


Interface design

Most of the work on the graphical side has been done by Eduardo Silva. He has set up a [ webpage] with images he designed and some comments about possible future changes.

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.

Update The size of the initrds is now down to around 10MB. Further reduction would be nice, but it is no longer a major issue.

Migrate from gtk+-directfb-2.0.9 to more recent version of GTK+ )

The udebs for gtk+-directfb are based on a [ set of sources] released in Apr 2003; it's now possible to build a set of libraries based on gtk+2.8.10 which was released around Jan 2006. The main problem is that [ building] is rather tricky, and there are no pre-patched sources available from upstream. Recently the Direct Frame Buffer backend was merged into GTK+ mainline and will be part of the upcoming GTK+ libraries version 2.10, whose release date is set around May 2006. Once upstream libraries will be ready to be used, they'll have to be packaged into udebs before we can use them in the installer.