diff options
| author | Danilo M. <danix@danix.xyz> | 2026-07-03 13:17:14 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-07-03 13:17:14 +0200 |
| commit | 84039594800902c30f3dfed8092b01f1a8620d68 (patch) | |
| tree | 016a215426c48432bcff1684889517e8f94a3190 | |
| parent | 21aabc67cb9e8e76c6fab6727690a3a9c02a98da (diff) | |
| download | mkhintfile-84039594800902c30f3dfed8092b01f1a8620d68.tar.gz mkhintfile-84039594800902c30f3dfed8092b01f1a8620d68.zip | |
docs: document dashed/underscore version normalization in README
Explain that upstream 2026-06-02 and packaged 2026_06_02 are treated as
the same version (SlackBuild versions cannot contain '-'), applied in
--check and --hintfile, with updates stored in underscore form.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
| -rw-r--r-- | README.md | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -166,6 +166,8 @@ When exactly one package is given, mkhint runs `nvchecker -e <package>` so only If any scanned hint file has no nvchecker source configured, `--check` lists those packages and offers to populate `nvchecker.toml` for them in one prompt — auto-detecting github/pypi from the SBo `.info`, otherwise writing a commented stub to fill in. After populating, it asks you to review the file (fill any stubs) and re-run `mkhint -C`. Packages with no matching `.info` in the repository are skipped. +Because a SlackBuild version string cannot contain `-` (it would break `PRGNAM` parsing), an upstream version such as `2026-06-02` is packaged as `2026_06_02`. mkhint normalizes upstream versions (`-` becomes `_`) before comparing them, so these are treated as the same version and no spurious upgrade or downgrade is offered. When you accept an update, the version is written to the hint file in the underscore form. The same normalization applies to `--hintfile` without `-v`. `nvtake` still records nvchecker's own raw upstream value. + ### Help ```bash |