• Roadmap

Scratchbox roadmap

Apophis (sb 1.0 -series)

R4 *RELEASED*

• Scratchbox snapshots (Automatic builds and tests from head)
• Bugfixes
• Maemo2.0 devkit
• Support for 0.9.8 toolchains

Rx (possible)

• bugfixes
• fakeroot optimization
• validate qemu with LTP, instead of just shipping minimal needed patches.

1.2 -series

Tool refactoring

The basic idea is to use full potential of the foreign tool wrapper so most of the tools can be used as is. The aim is to make it easy to bring new tools to scratchbox and pass the burden of maintaining tools back to the distribution maintainers.

In practice it means:

• Remove all tools (also from devkits)
• Debian binary devkit part of the base system
  • (but to a separate directory)
• Own debian repository for tools
  • Separate branches for sarge, etch and other distributions
  • mostly unmodified upstream packages(?)
  • Build only the ones that needs patching

Toolchain renovations

Possibility to use any foreign(gcc) toolchains easily in scratchox and get rid of the burden of maintaining own toolchains.

In practice:

• Support "only" for foreign toolchains (old toolchains are going to work too but we are not going to make new ones like that anymore)
• New runtime config format parsed from the config used by sb-toolchain-extras
• wrapper links should be generated at install time of toolchain instead of being statically predefined into the system

Other updates

Get rid of the problems related to old glibc (eg. VDSO issues), support AMD64 and make it possible to make windows devkit.

In practice:

• Host-gcc from gcc4 series with a matching glibc
• Support libsb to also run files with custom extensions (eg. exe)

SBRSH2

In practice

• See [http://www.scratchbox.org/wiki/Sbrsh2 Sbrsh2]

2.0 -series

• Integrate open redirector to scratchbox
• Remove all the patched tools
  • write lua scripts as needed
• Use new target structure where multiple targets can be active simultaneusly

Other ideas

• Show only cpu transparency methods relevant to the selected toolchain
• openVZ support (?)
• automatically use sysv fakeroot on host/qemu target
  • Even better, make faked accept both sysv and tcp connections(?)

Make using qemu-system+sbrsh emulator easy

• + Instead of emulating a selected set of syscalls in qemu, use the real target kernel
• - Need to create a minimal system image (linux+libc+busybox+sbrsh) for each toolchain

In practice:

• new cpu transparency method: qemu-system
• make a preconfigured minimal kernel+busybox+sbrsh image when creating a foreign toolchain
• when to start the system emulator?