Widen the accepted pimsync range to the 0.6 series; stream sync output and bound the Google HTTP calls

The version work and the sync-output work landed in one change; they can be
split apart if the history wants them separate.
This commit is contained in:
randogoth 2026-09-13 15:32:43 +03:00
parent 3d701361da
commit d03748472a
8 changed files with 250 additions and 94 deletions

View file

@ -25,7 +25,16 @@ Or straight from the repo, without cloning it first:
nix profile install "git+https://code.randogoth.com/randogoth/CalCalist.git#calcalist"
```
One runtime dependency is needed for CalDAV and iCal sync: **`pimsync` 0.5.11 or newer on `PATH`**. The Nix flake installation method already ensures this.
One runtime dependency is needed for CalDAV and iCal sync: **`pimsync`, from 0.5.11 up to but not including 0.7.0, on `PATH`**. The Nix flake installation method already ensures this: it builds pimsync from source and wraps `calcalist` so that copy is the one found, whatever else is installed.
To run a different pimsync — a fork, or a working tree — override the input at install time:
```sh
nix profile install "/path/to/calcalist#calcalist" \
--override-input pimsync-src "git+file:///path/to/pimsync"
```
The built pimsync reports the revision it came from (`pimsync 0.6.0-a08ee3c`), so the two are told apart. Note that `nix profile upgrade` does **not** remember an override: upgrading rebuilds against the default input, and the install command has to be repeated to get the fork back.
Then check the environment, which is worth doing before writing any config: