clearlinux/clear-linux-documentation
2
0
Fork 0
mirror of https://github.com/clearlinux/clear-linux-documentation.git synced 2026-07-09 06:06:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update mixer-about.rst

Browse Source 
Made a bunch of changes but didn't want to stomp on existing.
This commit is contained in:
Kevin Putnam
2018-12-03 14:03:14 -08:00
committed by Beth Dean
parent 4d54feeaf7
commit 7089de89fc
1 changed files with 16 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
source/clear-linux/concepts/mixer-about.rst
+16 -18
View File
@@ -4,35 +4,32 @@ Mixer
#####
|CL-ATTR| is a powerful, modular, and customizable OS. Upstream |CL| offers
many images for different deployment environments and use-cases. There are
many images to support different environments and use-cases. There are
hundreds of bundles that will meet most, if not all, of your OS and software
needs.
However, if you need additional customization or content, |CL| provides the
mixer tool to customize the OS. With mixer, there are two approaches to
customization:
mixer tool. There are two ways to customize the OS using the mixer depending
on the level of customization you need:
* :ref:`create-mix`
* :ref:`create-mixin`
Which approach you choose will depend on the level of customization that you
need.
1. :ref:`create-mix` to create a distinct derivative of the |CL| that
contains your custom software.
2. :ref:`create-mixin` using a lightweight wrapper of mixer to add custom
bundles to be included with an upstream version of the |CL|.
.. _create-mix:
Create a mix
============
The first approach is to use the mixer tool to create a derivative of the |CL|
that contains your custom software. This is known as creating a mix. In your
mix, you can
When creating a mix, you can
* Use any existing upstream bundles with no modification.
* Redefine what goes into existing bundles.
* Create completely new, custom bundles with your own custom packages.
With mixer you are not required to incorporate every upstream release into your
mix. You decide which upstream versions to update your derivative to, as
With mixer you are not required to incorporate every upstream release into
your mix. You decide which upstream versions to update your derivative to, as
illustrated in Figure 1.
.. figure:: figures/mixer-about-1.png
@@ -53,9 +50,9 @@ have a higher degree of control and customization of your custom |CL|.
Create a mixin
==============
The second approach is to use the mixin tool, a light wrapper for mixer, to
create custom bundles and sideload them into your upstream version of |CL|.
This is known as a mixin. A mixin is useful when you need to add custom or 3rd
The second option is to use the mixin tool, a light wrapper for mixer, to
create custom bundles and sideload them into your upstream version of |CL|.
A mixin is useful when you need to add custom or 3rd
party content but want to keep on the upstream update cycle, as shown in
Figure 2. You can also create new bundles using upstream packages.
@@ -75,8 +72,9 @@ not require breaking from upstream or acting as an OSV. With mixin
Related topics
==============
|CL| provides flexibility in how you customize your OS. Learn more about mixer
and related topics to decide which customization approach is best for you.
|CL| provides flexibility in how you customize your OS. Learn more about
mixer and related topics to decide which customization approach is best for
you.
* :ref:`mixer`
* :ref:`mixin`