This project aims to find a solution for creating and managing containers in a package-centric manner.
Every container will be able to specify their dependencies, which can be self-built packages or exact versions of already existing packages.
Like this the user will always exactly know what libraries, files, etc. is available to his container at runtime.
The specified container will have it's dependencies on packages which themselves can be packaged separately into one container per package.
*Source-based builds*
To allow maximum flexibility for the users, the package files must be able to describe source builds, which allows the user to make changes to the source before the package is built and integrated into the target container image.
*Reproducibility*
Builds of packages, as well as builds of container images, must be reproducible in a way that the same input always yields the same output.
Because every change of a package yields in a different identity, the system allows to have multiple versions of one software application.
These can differ in properties like source code patches, build configuration options, target architecture, etc..
*Portable buildsystem*
As a portable system, builds can be processed locally on a users workstation or distributed to a bunch of servers.
*Shareable source and binaries*
The build system will ship tools that make it easy to discover and share source and binary files that are respectively consumed and produced by the build system.
This will allow for very fast setups of containers that involve only downloading from trusted repositories.