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
|
KISS Linux Community Installation Guide
=======================================
Since Dylan is on a (permanent) hiatus, the KISS community is maintaining a set
of repos and a fork of the package manager. We have made enough minor changes
to the system that some differences to the install process should be noted.
Dylan's page (<https://kisslinux.github.io/install>) is still the canonical
reference. This page lists the differences to the official guide.
If you run into any problems, please join us in IRC (`#kisslinux` in
libera.chat) and ask.
- - -
## [%[001]] Tarball
(Official guide steps 001-005)
You should start with the updated rootfs tarball from the
[latest release](https://codeberg.org/kiss-community/repo/releases) which is
currently
[23.04.30](https://codeberg.org/kiss-community/repo/releases/tag/23.04.30).
Make sure you extract it *as root*. The tarball is not signed so step 004
doesn't apply. You should still verify the checksums though.
**NOTE** that the current release has a bug in the tarball; there are details
on the release page for the simple fix.
## [%[002]] Repos
(Official guide steps 007-009)
The core repos should be cloned from <https://codeberg.org/kiss-community/repo>.
For example, you might want to do something like this:
$ mkdir ~/repos
$ cd ~/repos
$ git clone https://codeberg.org/kiss-community/repo
$ export KISS_PATH="$HOME/repos/repo/core:$HOME/repos/repo/extra:$KISS_PATH"
You can put the repos wherever you like; `~/repos` is just an example.
Note that you should set `KISS_PATH` in your `.profile` so that it is set every
time you log in, rather than having to run the last line every time.
To make sure that kiss can find these packages, you can run
$ kiss s \*
(`*` needs to be escaped so that it isn't used as a glob for all the files in
your current working directory). The command should output every package found
in `$KISS_PATH` as well as all installed packages (listed in `/var/db/kiss/installed`).
Check that the paths like `~/repos/repo/core/...` show up.
We also maintain a community repo with many more packages than are found in
repo. You will probably want to use this; it can be found at
<https://codeberg.org/kiss-community/community> and enabled similarly to above.
## [%[003]] Commit signing
(Official guide steps 010-013)
`gnupg1` used to be used for signature verification but now commits are signed
with ssh (only for `repo`). To enable verification, run:
$ cd /path/to/repo
$ git config gpg.ssh.allowedSignersFile .allowed_signers
$ git config merge.verifySignatures true
## [%[004]] Kernel
(Official guide step 018)
`pkgconf` is used to detect `ncurses` when using menuconfig; install it with
$ kiss b pkgconf
There are a number of patches which may need to be applied to the kernel
depending on your version. Check the [FAQ page](/FAQ/#010) for details.
|
