renken/shione
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
experimental debian packaging for shione.net
51 commits 2 branches 0 tags 234 KiB
Shell 100%
Find a file
Renken b1b654331c
chore(gitignore): messy wip nextcloud config
2024-05-12 16:49:45 +02:00
config split into two commits one for nftables and one for srb2kart 2024-05-12 16:49:35 +02:00
deploy/shione srb2kart: read standard input from socket 2024-05-12 16:49:44 +02:00
nichijou nichijou: nvim: init lua config 2024-05-12 16:49:35 +02:00
.gitignore chore(gitignore): messy wip nextcloud config 2024-05-12 16:49:45 +02:00
.guix-authorizations guix-auth: authorize renken 2022-08-07 19:42:49 +02:00
.guix-channel rename repository to nichijou 2022-08-30 00:36:18 +02:00
.key key: add renken pgp key 2022-08-07 19:38:43 +02:00
LICENSE license: gplv3 2022-08-08 00:50:38 +02:00
README.md readme: debian configuration packages 2023-12-24 20:41:52 +01:00
TODO.md doc(todo): neovim packaging and configuration 2024-05-12 16:49:29 +02:00

README.md

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 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. 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

$ debuild
$ debuild -T clean