diff options
| -rw-r--r-- | TODO.md | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -5,9 +5,9 @@ - [~] split `mkhint` into multiple files — **deferred (2026-07-08).** 1568 lines / 46 functions with clear section markers is under the threshold where a split pays off, and bash has no module system: "split" means `source lib/*.sh`, which complicates the single-binary VM deploy (`scp mkhint` → copy a dir + fixed libdir, or a concatenate build step) and means auditing shared globals (`REPO_DIR`, `VERSION`, `FORCE`, config-source order) crossing file boundaries. Revisit trigger: file grows toward ~2500+ lines, OR a change to one area starts breaking an unrelated one, OR you can't find where something lives. When that happens, extract ONLY the self-contained bundled-dep block (`# ── bundled-dep manifest handling ──` … `# ── end`, already has begin/end markers and its own T-BM tests) as a single `lib/bundle.sh` — do not do a full teardown. - [ ] add a noDL column to `--list` similar to what we do with DelReq - [x] **v1.2.4:** suppress `prompt_continuation_urls` for manifest-listed packages (Phase 2 already corrects those lines; avoids the double-touch during the primary bump) - - [ ] **expand nvchecker source autodetection (priority):** map more upstream hosts than github/pypi in `add_nvchecker_section` (the single global emitter, used by `--new` and `--check` populate). Forges (owner/repo): gitlab, bitbucket, gitea.com, codeberg (gitea + `host`), pagure. Registries (name from URL, fall back to PRGNAM, else PRGNAM + `# verify`): npm, gems, cratesio, cpan, hackage, packagist, cran. Unrecognised → keep the `# TODO` stub. - - [ ] `--new`/`-n` prints the nvchecker stanza it appends (always, added or already-present), so I can see whether it needs hand-editing - - [ ] `--info`/`-i program`: print the relative path `category/program` highlighted (green) on top, then the program's README, paged if it doesn't fit + - [x] **v1.2.5: expand nvchecker source autodetection.** `_detect_nvchecker_source` maps github/gitlab/bitbucket/gitea/codeberg/pagure (owner/repo) plus pypi/npm/gems/cratesio/cpan/hackage/packagist/cran registries in `add_nvchecker_section` (single global emitter, used by `--new` and `--check` populate). github → `use_latest_release` + commented `use_max_tag`/`prefix` fallbacks; other forges → `use_max_tag` + commented `# prefix = "v"`; registries → name from URL via `_registry_name_from_url`, fall back to PRGNAM. Unrecognised → `# TODO` stub. + - [x] **v1.2.5:** `--new`/`-n` echoes the managed nvchecker stanza fenced on stdout (added or already-present, via `_extract_nvchecker_section`). + - [x] **v1.2.5:** `--info`/`-i program`: green `category/program` header then the README, paged with sticky header (`less --header=1`) only when taller than the terminal; missing pkg exit 2, missing README `(no README)`. Handler `show_info`. - [ ] `--check --dry-run`: report what would change across all listed packages without prompting or writing (audit before acting) - [ ] cache the manifest per run: `reconcile_bundle_deps` currently fetches it twice (report + apply); fetch once and reuse - [ ] verify md5 against the manifest `SHA256`: cross-check the downloaded file's sha256 against the manifest entry before writing MD5SUM (integrity check) |