diff options
author | P. J. McDermott <pjm@nac.net> | 2012-05-30 00:46:38 (EDT) |
---|---|---|
committer | P. J. McDermott <pjm@nac.net> | 2012-05-30 00:46:38 (EDT) |
commit | 76e712d8e48fca77a15f92f741ebff48be69bccd (patch) | |
tree | 3d56b66155b72ad329acfe1eb4ad11b334620430 | |
parent | 1c15a9405df33b3dd0400b25a3d63a42867a5447 (diff) |
Describe installation bootstrap tool work.
-rwxr-xr-x | dev.html | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -78,6 +78,9 @@ </ul> <p>In summary, there is much design work to be done, opkg and opkhelper must be modified to support multiarch, and certain packages will need to be built to handle multiarch library paths. Of course Debian is a great reference implementation, but there still remains much original work to be done.</p> <h3>Installation Bootstrap Tool</h3> +<p>A tool similar to <a href="http://anonscm.debian.org/gitweb/?p=d-i/debootstrap.git;a=tree">debootstrap</a> of Debian needs to be written to bootstrap the installation of a basic system. It can be used for building packages (see "Package Cross Building Tool" below) or installing the operating system on hardware targets.</p> +<p>Basically, the tool would fetch from the package archive the index of packages, determine which packages need to be installed, download each package, and unpack each package. Since the package manager may not be available, the tool must handle dependency resolution and package unpacking on its own.</p> +<p>We can't use debootstrap, since the formats of our binary packages and package archives differ slightly from those of Debian. But we can model our tool after debootstrap or even fork debootstrap.</p> <h3>Package Cross Building Tool</h3> <h3>Multiarch Toolchain Packages</h3> <!--#include file="includes/footer.html" --> |