Source Repositories
- Packages in Git
- Most source packages are maintained in Git repositories. To assist in the maintenance of a package, coordinate with its maintainer(s) and the system administrator.
- Documentation
- Notes, specifications, and policies are maintained in Git repositories.
- Web site
- These Web pages are maintained in a Git repository.
Specifications
- Source Package Format 1.0
- The format in which source packages are developed.
- Source Package Format 2.0
- The format in which source packages are developed.
- Architecture String Syntax
- The meaning of the architecture string for binary architectures and application platforms.
- Multiarch (to be written)
- The ability to install and use on a system packages built for multiple architectures.
Policies
Packages must adhere to a number of policies for distribution as part of this operating system.
- Packaging Policy (to be written)
- Requirements for package naming, splitting, and data.
- Filesystem Hierarchy Policy (to be written)
- The structure of the files and directories in the system.
- Software Inclusion Policy (to be written)
- Legal and technical requirements to protect user freedom and to ensure that all included software can be legally distributed and effectively supported.
Development Environment
All packages are cross-built using a toolchain consisting of kernel headers, GNU Binutils, GCC, and a standard C/C++ library. The cortexa8-linux-eglibc port, for example, is currently built using Linux-libre 3.2.7, GMP 5.0.2, MPFR 3.1.0, MPC 0.9, Binutils 2.22, GCC 4.6.2, and EGLIBC 2.15.
This operating system currently supports the following programming languages: C (ISO/IEC 9899 as implemented by GCC), C++ (ISO/IEC 14882 as implemented by GCC), UNIX shell command language (POSIX.1-2008 XCU), and microprocessor assembly languages (with syntax and directives as implemented in GNU as). Support for more languages (e.g. Perl and Python) will come as their respective interpreters and compilers are packaged; this may take time as these programs usually have many build-time and run-time dependencies and some of these programs cannot easily be cross-built.
Remaining Tasks
There are a number of development projects that remain to be done.
- Boot Sequencing
- A flexible method of determining the order in which init scripts should be executed.
- Multiarch
- The ability to install and use packages built for non-native architectures.
- Installation Bootstrap Tool
- A tool to bootstrap the installation of a basic system.
- Package Cross Building Tool
- A tool to build packages within a chroot environment
- Multiarch Cross Toolchain Packages
- Packages of toolchain components that use multiarch library paths.
- Packaging
- Software that should be packaged soon.
- Removing libbb from opkg
- The modification of opkg to dynamically link against a newer libbusybox.