DOSContainers
/
doscontainer
2
0
Fork 0
Code Issues 6 Pull Requests Packages Releases Wiki Activity

Clarify layered architecture.

This commit is contained in:
Bas Wiel, van de 2024-04-18 11:39:14 +02:00
parent cc6845bb35
commit 3023701bbe
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/design.tex
View File

@ -5,7 +5,9 @@ DOSContainer follows a number of design and philosophical principles.
\item DOSContainer is \textbf{predicated on layers}, much like Docker containers. It pulls in many parts,
layers them on top of each other and composes a disk image as the finished result. You can then use
that image file to run software on either an emulator or even a real vintage computer, given a way
to transfer the image there.
to transfer the image there. The layers ensure that mixing and matching of all components of a software
environment is possible. It gives the end user the ultimate flexibility in using the manifest files to
output any out of potentially thousands of different permutations without ever touching the DOS environment itself.
\item \textbf{Native binary, fully self-contained}. This means DOSContainer itself will never be more than
a single executable file for any platform. This eases both distribution and use. Just drop the file
anywhere on your system and it will just work.