The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Kickstarter
(→Declarations) |
(→Configurations) |
||
| Line 38: | Line 38: | ||
== Configurations == | == Configurations == | ||
| − | The "Configurations" keyword is a list, specifies which kickstart files should be generated | + | The "Configurations" keyword is a list, specifies which kickstart files should be generated, see example above |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
== Inheritance == | == Inheritance == | ||
Revision as of 13:13, 11 February 2012
Mer Kickstarter
YAML
External configurations
The "ExternalConfigs" keyword will tell kickstarter to look for additional YAML files to parse. Lists will be merged in order of inclusion, ie, if there is a key/value pair, the latest YAML file to be included (or the one having ExternalConfigs and that key), will specify the final value corresponding to the key. When lists are merged, later yaml file contents always will be first in the list, earlier ones appended.
"ExternalConfigs" should be accompanied with a list of directories.
Example:
ExternalConfigs: - /usr/share/kickstarts/mer-core - /usr/share/kickstarts/n900-hard
Declarations
There are two types of objects in a kickstarter file, one is declarations and one is configurations.
Declarations are sets of descriptions which has a name. These cannot inherit from each other.
Configurations are what is actually getting made into kickstart files, has to have a name and a filename.
Example:
Foo:
Kernel: kernel-foobar
Configurations:
- Name: Mer Core for foobar
FileName: mer-core-foobar
Inherits:
- Foo
Groups:
- Mer Core
Configurations
The "Configurations" keyword is a list, specifies which kickstart files should be generated, see example above
Inheritance
Example:
Inherits:
- foo
- bar
