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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
|
===========================
Install and Remove `kw`
===========================
.. contents::
:depth: 1
:local:
:backlinks: none
.. highlight:: console
Package Dependencies
--------------------
You have to figure out the correct package name in your distro for the
following dependencies:
* libguestfs
* Qemu
* Ansible
* Bash
* git
* python-docutils
* rsync
If you want to use the default alert system (for commands that may take longer
to run), you also have to install:
* paplay
* notify-send or dunst
For development, you will need:
* dash
* shunit2
* fish
For getting the Sphinx Documentation:
* Sphinx
Recommendations
~~~~~~~~~~~~~~~
If you want to use Qemu, we suggest the following steps:
1. Create a Qemu image;
2. Create a working directory in your host machine at: `mkdir -p ~/p/mount`;
3. After you have your working QEMU image, we recommend you to setup basic
stuff (this can vary depending on the distribution you choose - kernel setup,
ssh, etc);
Install
-------
Manual install
~~~~~~~~~~~~~~
In the kw's directory, type::
./setup.sh -i
bash --login
This command will install `kw` in `~/.config/kw`, and append the following
lines at the end of your `.bashrc`.::
# kw
PATH=$PATH:/home/$USER/.config/kw
source /home/$USER/.config/kw/src/bash_autocomplete.sh
If you use another shell (`ksh`, for example), you will need to manually add
the path to `kw` to `PATH` environment variable.
To check if the installations was ok, open another terminal and type::
kw help
Package install
~~~~~~~~~~~~~~~
- Arch Linux:
Available at AUR: https://aur.archlinux.org/packages/kworkflow-git/
Update
------
Every time you want to get a new version of `kw`, just pull from this
repository and install kw again (`./setup -i` removes legacy files and installs
new ones).
Remove
------
There's two way to remove kw: soft and hard way. The soft way (recommended
method) does not remove .config files under kw management and you can type::
./setup.sh --uninstall # or just -u
.. warning::
Beware: that the following command is dangerous! Use it only if you are
entirely aware of what are you doing.
If you want to remove all files under kw management, you can use::
./setup.sh --completely-remove
Global Configuration File
-------------------------
All the default configurations adopted by kworflow can be seen at
`~/.config/kw/etc/kworkflow.config`; this config file has a comment on each
configuration option. Finally, it is essential to highlight that kw loads the
default configurations; next, it tries to find a local configuration file
(detailed ahead) and overwrites the global options with the ones read from the
local config file. In summary, the local config has higher precedence than the
global config.
Local Configuration File
------------------------
Kw allows you to have a specific set of configuration per project. For example,
if you have a particular kernel tree named ‘drm-work’ and want a different
configuration from the default you can follow these steps:
1. Copy `kw.config.example` as follows::
cp kworkflow.config.example /PATH/KERNEL/SOURCE/kworkflow.config
.. note::
The default name **must be** `kworkflow.config`
2. Change the options inside::
qemu_hw_options=-enable-kvm -daemonize -m 3G -smp cores=4,cpus=4
qemu_net_options=-net nic -net user,hostfwd=tcp::2222-:22,smb=$HOME
qemu_path_image=$HOME/p/virty.qcow2
3. Done! Every time you execute any command in the root dir of drm-work the
configuration file will be read. If the file does not exist, the default
operation will be used.
|
