renken/shione
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

readme: debian configuration packages

Browse source
This commit is contained in:
Renken 2023-12-24 20:41:52 +01:00
parent b9c16947df
commit a7ce0c374f
Signed by: renken
GPG key ID: 1F2BB159B645E575
1 changed files with 32 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

49
README.md
View file

@ -1,35 +1,50 @@
# Nichijou # Nichijou
Experimental Guix packaging and configuration. This project is mainly for Experimental Debian packaging and configuration. This project is mainly for
educational purposes. However, the aim is to produce a per-host shared educational purposes. However, the aim is to produce a per-host shared
configuration that would suit my real world usage. configuration that would suit my real world usage.
# Siga ## Host machines
My personal computer which runs GNU/Linux Debian testing. ### Siga
## TODO [Desktop PC](https://shione.net/log/archive/2023/06/1687104871/index.html)
running GNU/Linux Debian stable.
# Shione ### Tabi
My GNU/Linux Debian stable sever which is no longer operation, it will have a Lenovo Thinkpad x260 laptop running GNU/Linux Debian stable.
basic home configuration with only neovim on it.
## TODO ### Shione
* Perhaps a bash configuration that is produces essentials of the zsh one? NiPoGi CK10 with the Intel Core i7-10810U Mini PC server running GNU/Linux
Debian stable.
# [insert work computer name here] ## HOWTO
My work computer which should run GNU/Linux Debian either stable or testing. It Because all of my machines run GNU/Linux Debian, I wish to transform
doesn't exist yet. 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.
## TODO 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.
* Neovim and zsh. ## Project hierarchy
# Configuration TODOs 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`.
# Packages TODOs ### NOTES
* mpv-webm ```console
$ debuild
$ debuild -T clean
```