The SysRoot Pattern: Part One

Abstract

Acting as the software distribution for NeKernel. this was developed to hold the its components and sysroot altogether.

The SysRoot Rationale:

There is three main reasons for this repository's existence:

• Hold the codebase in a single repository, which is way more maintnable than a fragmented one.
• Easier path resolutions based on a virtual root path, i.e (../kernel -> /src/kernel)
• Make releases cycle easier to document and deploy than before.

Why a SysRoot?

There is two reasons for a sysroot architecture:

• We avoid deployment scattering.
• Easier tooling can be written for such repositories. e.g: checkpath.py, mkfs.py.

Conclusion:

A SysRoot architecture guarantees a sound and verifiable architecture for embedded and general software systems. Use it wisely to prepare software deployments.