Marty Oehme
280fab6ad3
Package list is now a single tab separated list. That should make several automations in the future much simpler. The table is built as follows: `Name Description Source Target` with one line per package. Source denotes official repositories or AUR, and target is kept for future potential of creating different deployments per target automatically (e.g. different package list for desktop and server, and so on). There is an updater script `bootstrap/update_package_list.sh` which will automatically populate the table, removing uninstalled packages, adding new ones and (making its best attempt to be) keeping the selected targets as they are. The git commit hook comparing installed and committed packages has also been rewritten to use the new table and be a little simpler overall. Fixes #2. |
||
|---|---|---|
| .. | ||
| .config/sh/alias.d | ||
| system-packages/etc/keyd | ||
| .stow-local-ignore | ||
| install_packages.sh | ||
| packages.tsv | ||
| README.md | ||
| update_package_list.sh | ||
bootstrap module
The bootstrapping module mainly concerns the setup of the repository itself -- installation of packages, setting up basic options and maintenance scripts.
- installs general list of packages, listed here
- if githooks are enabled (either through install script, or manually) will compare installed packages with those on the package list on each commit and warn user about differences
- contains a simple alias
dotlinkwhich allows quickly re-linking dotfiles when they have been changed. This is useful to invoke when files have been removed or added and need to be sym-linked by stow again (only works for~/.dotfilesdot directory) - contains an
update_package_list.shscript which I can use to quickly repopulate the list of explicitly installed packages, noting down their source (repositories or AUR) and retaining their target, if I set any (only works for~/.dotfilesdot directory)