criew 0.0.3

Terminal-first Linux kernel patch mail workflow TUI
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126

# Install and Setup

This page covers the environment requirements,
supported install paths,
`b4` resolution,
and the first commands to verify a CRIEW installation.

## Prerequisites

- Rust stable
- Git
- Python 3
  Python 3 is required when CRIEW uses the repo-local `vendor/b4/b4.sh`
  or the embedded runtime fallback.
- `b4`
  CRIEW resolves `b4` in this order:
  `[b4].path` ->
  `CRIEW_B4_PATH` ->
  `./vendor/b4/b4.sh` ->
  the embedded runtime copy under `~/.criew/vendor/b4/b4.sh` ->
  `b4` in `PATH`.
- `git send-email`
  This is required only when you want to send replies.

Run `criew doctor` after installation.
It checks `b4`,
`git send-email`,
git mail identity,
and IMAP connectivity.

## Installation

### Install from crates.io

Use this as the default path:

```bash
cargo install criew
```

This build embeds a minimal vendored `b4` runtime.
If `[b4].path`,
`CRIEW_B4_PATH`,
and `./vendor/b4/b4.sh` are all unavailable,
CRIEW can materialize that fallback under `~/.criew/vendor/b4/` on first use.
Python 3 is still required for that fallback.

### Install from a clone

Use this when you want the checkout-local `./vendor/b4/b4.sh` fallback:

```bash
git clone --recurse-submodules https://github.com/ChenMiaoi/CRIEW.git
cd CRIEW
cargo install --path . --locked
```

If the repository is already cloned without submodules:

```bash
git submodule update --init --recursive
```

### Install directly from GitHub

```bash
cargo install --git https://github.com/ChenMiaoi/CRIEW.git --locked criew
```

In this mode,
provide `b4` through `b4.path`,
`CRIEW_B4_PATH`,
or your system `PATH`.
If the checkout also includes `vendor/b4`,
CRIEW can use it the same way as a source clone.

### Run from source

```bash
cargo run -- doctor
cargo run -- tui
```

## Runtime naming baseline

`v0.0.1` is the first supported public baseline.
From `v0.0.1` onward,
CRIEW supports only:

- `criew`
- `~/.criew/`
- `criew-config.toml`
- `criew.db`
- `CRIEW_B4_PATH`
- `CRIEW_IMAP_PROXY`

Courier-era names are not a supported upgrade path.
If you tested older pre-release snapshots,
refresh your checkout or reinstall the binary
and bootstrap a new CRIEW runtime directory with the CRIEW naming set.

## Verify the result

Run:

```bash
criew doctor
criew version
```

A `v0.0.2` release build should report `criew 0.0.2`
from `criew version`.

Success means:

- CRIEW starts without runtime bootstrap errors.
- `b4` resolves from a configured path,
  a vendored fallback,
  or `PATH`.
- `git send-email` is reported only if you plan to send replies.

## See also

- [Configuration](Configuration.md)
- [Sync and TUI](Sync-and-TUI.md)
- [Repository source](https://github.com/ChenMiaoi/CRIEW)