File: manipulating-kw-config-file.rst

package info (click to toggle)
kworkflow 1%3A0.6.2-1~exp1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 4,148 kB
  • sloc: sh: 22,233; perl: 2,172; ansic: 96; python: 72; sql: 28; makefile: 19
file content (30 lines) | stat: -rw-r--r-- 1,020 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
======================================
  How to manipulate kw config options
======================================
.. _manipulating-kw-config-file:

.. contents::
   :depth: 1
   :local:
   :backlinks: none

.. highlight:: console

kw has multiple configuration files, many associated with a specific feature
since we follow the pattern <feature-name> has <feature-name.config> file. For
example, ``kw build`` reads the ``build.config`` file to get the user's
parameters.  kw config file syntax is straightforward, it just follows::

  <option> <value>

Users can open any config file at ``.kw/`` and manually change it. However,
this is far from convenient, and manually changing a file should be avoided
since we have a dedicated command to interface with those files. This command
is the ``config`` option which you can use like this::

 kw config <config-name.option> <value>

For example, suppose you want to use the kernel ``menuconfig`` option instead
of the ``nmenu``::

 kw config build.menu_config menuconfig