Marty Oehme
1a05ea8445
Split the lists into two, with testing getting automatically updated on packages added (and removed, but only if the package to be removed is *not* in stable packages already). This way, I can always be sure that I have my stable setup in the repository, but packages that I am temporarily testing have a place without being forgotten and I can more easily change them around until they find a place in stable or get thrown out. |
||
|---|---|---|
| .. | ||
| .config/sh/alias.d | ||
| system-packages/etc | ||
| .stow-local-ignore | ||
| install_packages.sh | ||
| packages_stable.tsv | ||
| packages_testing.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)