diff --git a/content/designs/hwpack-requirements.md b/content/designs/hwpack-requirements.md index 6ae0cf0a1567a954390352a31e309ac79f85dbf0..7c207ff3daaff9dc2c90745224d160afa2e681e0 100644 --- a/content/designs/hwpack-requirements.md +++ b/content/designs/hwpack-requirements.md @@ -26,7 +26,7 @@ The selection and packaging of these packages are predominantly driven by the ne The OSpack stage generates one or more generic (architecture specific but largely hardware independent) archived rootfs built from Apertis packages. These rootfs archives are known as OSpacks. The process is managed by a tool called [Debos](https://github.com/go-debos/debos), which uses yaml configuration files to guide what steps it takes. Apertis provides yaml files to assemble a number of differently targeted OSpacks, ranging from a minimal GUI-less OSpack, a target focused GUI OSpack and a development environment with a desktop style GUI and has pre-packaged the components required to generate these OSpacks. - + #### HWpack diff --git a/content/designs/media-management.md b/content/designs/media-management.md index 0dfe5acdd8fc3acac50feb7b31bddad0b0b51ea5..c7d5004a5ee5c9d79f93a5bfbcde85600daf26a0 100644 --- a/content/designs/media-management.md +++ b/content/designs/media-management.md @@ -142,7 +142,7 @@ See this illustration for an overview of the general architecture. Some of the components listed will be introduced with more detail in the following chapters. - + ### **Local Storage Media Source** @@ -257,7 +257,7 @@ involved. **Status**. Satisfied. - + #### **Paged queries** @@ -538,7 +538,7 @@ regarding the type of tasks and their priority, as well as test for other ideas during the development. Requirement R12 has more details about the abstraction of different types of tasks in the queues. - + #### Media Content Counters