diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-02 12:16:38 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-02 12:16:38 -0500 |
| commit | b10cba594db836c0747066addad48bda4d30cd02 (patch) | |
| tree | 063119a623fa3f7139feda4ef302896d8f5f934c /dotfiles/common/.zsh/modules/Test/README | |
| parent | 49c2ba9c4510bf6e1acd306687473bc8ba9ad8dd (diff) | |
| download | archsetup-b10cba594db836c0747066addad48bda4d30cd02.tar.gz archsetup-b10cba594db836c0747066addad48bda4d30cd02.zip | |
refactor: drop in-repo dotfiles/, move stow tooling to the dotfiles repo
Since the installer clones DOTFILES_REPO into ~/.dotfiles and stows from there, the in-repo dotfiles/ tree was dead weight. Nothing reads it at install time. I removed it (831 files) now that both machines are migrated.
The Makefile's stow / restow / reset / unstow / import targets and the dotfile-script unit suites moved to the dotfiles repo. They sit alongside the scripts they manage and run standalone (cd ~/.dotfiles && make ...). This Makefile keeps the VM-integration targets and the installer-helper suite (safe-rm-rf).
I updated CLAUDE.md and README.md so stow operations run from ~/.dotfiles, and the dotfile-management, theme, and unit-test sections point at the standalone repo. The README was already describing the old in-repo model from before the installer switched to cloning. This brings it in line.
Diffstat (limited to 'dotfiles/common/.zsh/modules/Test/README')
| -rw-r--r-- | dotfiles/common/.zsh/modules/Test/README | 30 |
1 files changed, 0 insertions, 30 deletions
diff --git a/dotfiles/common/.zsh/modules/Test/README b/dotfiles/common/.zsh/modules/Test/README deleted file mode 100644 index d012277..0000000 --- a/dotfiles/common/.zsh/modules/Test/README +++ /dev/null @@ -1,30 +0,0 @@ -There are now different sections, expressed by the first letter in the -scripts names: - - A: basic command parsing and execution - B: builtins - C: shell commands with special syntax - D: substititution - E: options - V: modules - W: builtin interactive commands and constructs - X: line editing - Y: completion - Z: separate systems and user contributions - -You will need to run these by using `make test' in the Test subdirectory of -the build area for your system (which may or may not be the same as the -Test subdirectory of the source tree), or the directory above. You can get -more information about the tests being performed with - ZTST_verbose=1 make check -(`test' is equivalent to `check') or change 1 to 2 for even more detail. - -Individual or groups of tests can be performed with - make TESTNUM=C02 check -or - make TESTNUM=C check -to perform just the test beginning C02, or all tests beginning C, -respectively. - -Instructions on how to write tests are given in B01cd.ztst, which acts as a -model. |