aboutsummaryrefslogtreecommitdiff
path: root/.stignore
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-08-21 02:09:35 -0700
committerCraig Jennings <c@cjennings.net>2026-08-21 02:09:35 -0700
commitcfe9ab2c9a23757bf23d827c22d183e42f458541 (patch)
tree3b57e17931ce41587f1b41fb85905cce49c70bfc /.stignore
parente312829a5b6175b7826088a55522afb89733b219 (diff)
downloadarchsetup-cfe9ab2c9a23757bf23d827c22d183e42f458541.tar.gz
archsetup-cfe9ab2c9a23757bf23d827c22d183e42f458541.zip
fix(cmail): let Bridge setup finish without cmail-action
I moved the cmail-action install out of cmail-setup-finish.sh and left behind a guard that aborts when the tool is missing. The script mentions cmail-action five times and invokes it zero — every hit is a comment or that check. So a Bridge provisioning script hard-failed over a mail client it never touches, and a fresh machine got Bridge ready, the cert exportable, the service startable, and a script that refused to configure any of it. It warns with the same remedy and carries on now. That also drops an ordering neither repo needs: Bridge setup no longer requires rulesets cloned and installed first. The sequence around it hadn't caught up either. Both the checklist and the installer's completion message still opened with "clone claude-templates to ~/projects/claude-templates", the same dead path that broke the script, and neither mentioned rulesets at all. So the documented order was: clone a stale repo to a path that doesn't exist, log into Bridge, then run a script that aborts pointing at a directory nothing created. Both now run Bridge first and name rulesets as what it is — not a prerequisite for those steps, but the thing mbsync wants. I also rephrased the header claim that the symlink "arrives on its own". True on a machine that runs agent sessions, since session start runs make install, and false on one that doesn't. It states the condition now instead of the consequence.
Diffstat (limited to '.stignore')
0 files changed, 0 insertions, 0 deletions