blob: c1b194086286364e8255ac84a491ac9964c43e8c (
plain) (
blame)
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
|
# Nichijou
Experimental Debian packaging and configuration. This project is mainly for
educational purposes. However, the aim is to produce a per-host shared
configuration that would suit my real world usage.
## Host machines
### Siga
[Desktop PC](https://shione.net/log/archive/2023/06/1687104871/index.html)
running GNU/Linux Debian stable.
### Tabi
Lenovo Thinkpad x260 laptop running GNU/Linux Debian stable.
### Shione
NiPoGi CK10 with the Intel Core i7-10810U Mini PC server running GNU/Linux
Debian stable.
## HOWTO
Because all of my machines run GNU/Linux Debian, I wish to transform
per-package config into `.deb` packages themselves. This project is basically
an application of
[`config-package-dev`](https://debathena.mit.edu/config-package-dev/). This
will allow me to integrate the modifications I introduce to the said packages
within the Debian packaging system which comes with many benefits.
1. Quickly rebuild a host machine from scratch if needed.
2. Know the configuration state of each machine using the package manager.
3. Automatically update configuration by updating the system itself.
4. Integrate complex post-installation configuration, possibly such as
introducing cron jobs (is it possible?) as part of the configuration
package.
## Project hierarchy
It is not yet clear to me how I'll do this. I'm thinking perhaps
`config/$host/$package` with the exception of `config/generic/$package` for
host-generic packages such as `neovim` for `siga` and `tabi`.
### NOTES
```console
$ debuild
$ debuild -T clean
```
|
