NEWS

Version Beta 0.12.3
=====
- Update: slacker-cli
    - update repo list.
- Update: slacker-gui
    - update crates
---

Version Beta 0.12.2
=====
- Notes:
    - From now on the development for `x86_64` and `i686` will happen to "developing" branch
      main branch will be there only for `Cutting a Release`.
      `aarch64` has its own independent branch for developing and releases thanks to @n4t3r.
    - A new source tarball (slacker-version.tar.gz) will be added on release page for packagers.
      This tarball will include only what a packager need for build and package slacker from main branch.
      This tarball will created from `scripts/make-source.sh` script (added).
    - @conraid offered to package slacker for slackware64-current. (thank you!)
      We recommend that you activate his repository so that every time a new version is released,
      it will be automatically downloaded in the updates.
      This is also the best way to satisfy @danix #10's fair request without messing with the code just for slackware64-current :)
- Update: slacker-cli
    - after perl changes version, slacker lists the installed packages
      still living in the old perl tree, so you know what needs rebuilding.
    - slacker now detects a running graphical session from the system itself
      rather than from its own environment, so the "log out and use a console"
      advice is correct when it runs under pkexec (slacker-gui), su or sudo,
      which drop DISPLAY and WAYLAND_DISPLAY.
- Update: slacker-gui
    - the transaction window gives the command output the room it needs while
      a question is on screen; a question's options are laid out side by side.
    - headings and captions now follow the desktop font size (and the window
      zoom) like the rest of the window, instead of staying at the fixed point
      sizes libadwaita gives them.
---

Version Beta-2 0.12.1
=====
- NOTE: slacker-cli (v0.12.1) has no changes, this version has fixes for slacker-gui only(vBeta_2).
- Update: slacker-gui
    - font sizes follow the desktop. The stylesheet pinned a dozen sizes in
      absolute points, so those parts of the window ignored the font size set in
      the desktop while the rest followed it; they are ratios now, and
      everything scales together. Reported by @danix (issue #9).
    - zoom: Ctrl with the wheel, or Ctrl with +, - and 0, scales the whole
      window between 70% and 250% of the desktop's font size. The choice is
      remembered in ~/.config/slacker-gui/zoom.
    - blocks of slacker's own output are no longer clipped when the font is
      large. They were drawn in a TextView, which is scrollable and therefore
      has a minimum height of zero, so inside a preferences group it collapsed;
      a label measures the text it holds.
- Fix: slacker-gui
    - the "nothing has been printed" notice no longer appears during kernel
      upgrades, when dracut is simply quiet while it builds the initrd. It now
      waits much longer unless the last line really reads like a question, and
      when it does appear it says so calmly instead of looking like an error.
---

Version Beta 0.12.1
=====
- Update: man page and wiki pages
- Update: cmd: slacker show-changelog for repos: {alienbob,restricted,patches,extras,testing}
- Update: cmd:slacker find-mirror suggest only mirros in sync
- Update: rc.local_shutdown added to protected files too.
- Update: prepare slacker code for aarch64 support.
- Fix: cmd:slacker status
    - the Pkgtools row no longer reports installpkg/upgradepkg/removepkg as
      MISSING when `status` runs as a plain user. Slackware's /etc/profile puts
      /sbin on root's PATH only, so a user (or slacker-gui, which runs `status`
      unprivileged) saw a false error. The check now looks on $PATH and in
      /sbin. Nothing changed in how the pkgtools are executed: they still run
      as root, where /sbin is on the PATH.
- Update: cmd:slacker revert-pkg
    - the cumulative archive is now read BEFORE you are asked to choose a
      version, so an archive that cannot serve the rollback is reported up
      front instead of after the selection.
    - three situations that used to end in the same confusing message are now
      told apart: an archive that answers with a package list that has no
      packages yet, an address that does not return a package list at all
      (a typo in CUMULATIVE_URL, an error page), and an archive that cannot be
      reached. A package that is not in the list at all is also reported
      before the prompt.
    - when the package is listed but that particular build is no longer in the
      tree, slacker prints the exact URL where the release archive keeps it and
      the CUMULATIVE_URL to set if you want it. It never switches archive by
      itself: which repository to trust stays the admin's decision.
    - why this matters: from 16.0 on, slackware.uk moves the whole cumulative
      -current tree into the archive of the release when that release is made,
      and copies the fresh release package set back in its place. Signatures
      travel with the packages, so verification is unaffected, but for a while
      after each release the -current archive holds one version per package and
      has nothing older to offer. That is now a clear message, not an error.
- Fix: shared code on non-x86 architectures (no change on x86)
    - `status` no longer compares your mirror against the x86 tree on the
      upstream reference mirror when the system is not x86. That reference
      carries no Slackware ARM trees, so the freshness verdict was meaningless
      there; it is now reported as not checked.
    - `find-mirror` stops with an explanation instead of probing the official
      mirror list, which lists x86 trees only, and proposing lines for the
      wrong architecture.
    - the kernel reminder now also recognises Slackware ARM's `kernel_armv8`,
      and the LILO/ELILO/GRUB line is printed only for an x86 kernel package.
    - the default CUMULATIVE_URL on aarch64 points at the aarch64 cumulative
      tree instead of the 32-bit x86 one.
---

Version Beta 0.12.0
=====
- SEMANTIC CHANGES: We don't like this but it has to be done...
    - So, slacker in the binaries produced by this repository is moving from `/usr/local/sbin` which has been in `/usr/bin/` until now.
      There are many reasons and against my will. But it has to go there instead of `/usr/local/bin` so that we can prepare it
      according to SBo standards which is our goal when slackware-16.0 comes.
    - However, those who build slacker themselves should know that it has been designed to work in `/usr/local/{sbin,bin}` as well as in `/usr/{bin,sbin}`
      so in any of the 4 paths it will be fine!
- Add: slacker-gui, (OPTIONAL) because why not?
    - GTK4/libadwaita front-end for slacker. It contains no package logic:
    - it runs the slacker binary, reads what slacker prints, and lays it out.
    - Nothing from slacker code was touched and nothing will be. The real slacker lives in cli.
    - Requirements: Everything exist in a stock Slackware-current installation:
      1. GTK >= 4.0, libadwaita >= 1.5 (the development branch ships 1.9),
      2. gtk4-rs 0.10 / libadwaita-rs 0.8, rustc >= 1.83,
      3. A polkit authentication agent in the session.
    - Note: slacker-gui freeze it`s version when slacker freezing, so from now on:
      `0.12.0` <-- belongs to slacker AND to slacker-gui belong --> `_beta_1`
    - That said, hopefully when slackware-16.0 released slacker will freeze --> `slacker-16.0_RC_0`
      and in few days will be a ready and stable `slacker-16.0`
- Update: Rearrange folders and repository structure:
    - For obvious reasons, there was a major rearrangement...
- Update: wiki pages.
---

Version Beta 0.11.9
=====
- Update: cmd:slackernew-config
    - give each protected file its own reason (cosmetic fix previous commit)
- Update: cmd:slacker new-config
    - the five files Patrick's upgrade HOWTO skips — /etc/passwd, /etc/shadow,
      /etc/group, /etc/rc.d/rc.inet1.conf and /etc/rc.d/rc.local — are never
      replaced by their .new, whatever is answered. Replacing them wholesale
      deletes every account or the network configuration, and the .orig backup
      is no help once login is impossible. They are flagged in the list and a
      warning explains what to do instead (merge by hand with P then M); their
      .new files are left in place.

- Update: cmd:slacker upgrade-dist
    - `new-config` gains an "(A)ll new" choice during a dist-upgrade only:
      install every incoming config and keep the previous one as .bak, the
      shape of the script in Patrick's HOWTO. The protected five are skipped
      there too.
    - the pre-reboot REMINDER (slacker does not run any of these itself) now
      follows the 15.0 -> 16.0 HOWTO: geninitrd first (it also updates
      grub.cfg), then lilo / grub-install (UEFI and BIOS) / eliloconfig, and a
      note for USB-stick booting.
- Fix: typos in main.rs
---

Version Beta 0.11.8
=====
-Update: wiki docker file
- Update: repo-name commands
    - writing a repo as '@name' where the command takes plain repo names
      (`install-new @ponce`) now suggests the plain name instead of
      reporting '@ponce' as an unknown repo. Applies to install-new,
      clean-cache, vet-repo, trust-repo, distrust-repo, del-repo and
      pri-repo.
- Fix bug: cmd:slacker install, cmd:slacker download, cmd:slacker upgrade,
  cmd:slacker reinstall
    - mixing a package name with an @repo selector (`install fontforge
      @conraid`) selected the package AND the entire repo, then offered
      the lot behind a prompt that takes everything on [Enter]. It is now
      refused with the correct syntax; @repo on its own still takes a
      whole repo, and a `repo:name` pin may still sit next to it.
- Fix bug: cmd:slacker install, cmd:slacker download, cmd:slacker upgrade,
  cmd:slacker reinstall, cmd:slacker remove
    - an argument that matched nothing was reported and then ignored, so
      the command acted on the rest: `download fontforge ponce` (a dropped
      `:`) fetched fontforge from conraid while the user was reading "no
      match for 'ponce'", and a mistyped `remove` argument would take out
      the packages that did match. Any miss now refuses the whole command,
      as apt, dnf and pacman do; `-y` does not bypass it. install-new,
      upgrade-all and upgrade-dist are unaffected: they expand @repo
      internally and an empty repo must stay harmless.
- Update: miss reporting
    - an argument that names a repo or a build tag is no longer answered
      with the closest package name ('ponce' -> 'poke'). It says what the
      word actually is and gives both selector forms, `repo:<package>` and
      `@repo`.
---

Version Beta 0.11.7
=====
- Update: Add new repo (slackpack)
- Fix bug: cmd:slacker history
    - an upgrade line took its source label from the OLD build, so a package
      replaced by one from a different repo was credited to the repo it had
      just left: `libjxl 0.12.0-1_SBo -> 0.12.0-1` read as [SBo] although it
      landed in the official tree. The label now comes from the replacement.
      Installs, removals and upgrades whose successor could not be identified
      still describe the only build they have.
---

Version Beta 0.11.6
=====
- Update: cmd:slacker upgrade-dist
    - Add mkinitrd in core packages as Patrick did for slackpkg, read ChangeLog:
      Sat Aug 29 04:22:54 UTC 2026
      Install mkinitrd early because the kernel might need the latest version.
- Fix bug: cmd:slacker history
    - an interrupted upgradepkg can leave a renamed `<pkg>-upgraded-<T>`
      record behind in the packages/ admin dir, before it gets moved to
      removed_packages/. history read that directory without the filter
      installed_packages already applies, and PkgId::parse does not reject
      such a name -- it mis-splits it -- so the leftover showed up as a
      phantom installed package, with a bogus version and source label.
      history now skips these records, so search and history agree on what
      is installed. Creating the leftover is pkgtools' business; slacker
      just stops reporting it as a package.
- Fix bug: cmd:slacker search
    - the "not in any repo, but installed" fallback matched the installed
      name case-sensitively, while repo names are matched case-insensitively.
      So `slacker search orbit2` answered "No package named 'orbit2'" (exit
      20) for a package that `slacker search ORBit2` reported as installed.
      The builds this branch exists for -- SBo and local ones -- are exactly
      the ones with capitals in their names. Both spellings now find it, and
      the messages name the package by its real id, so the suggested
      `slacker info <name>` works as printed.
---

Version Beta 0.11.5
=====
- Fix bug: cmd:slacker update, cmd:slacker check-updates
    - a repo whose metadata cannot be fetched (bad URL, 404, DNS) is now
      reported as unreachable instead of "new (will update)"; it is still
      retried, but nothing is promised that will not happen.
    - the update prompt counts repos "to update" rather than saying they
      all have updates.
- Fix bug: cmd:slacker info -- becomes the command that knows the local world too.
           cmd:slacker search -- when it doesn't find anything, does a cheap check:
           if the name is installed, it says so on one line instead of blindly referring to info
- Fix: "wiki: restore Blacklist translations to dotted filenames"
- Updated rusqlite 0.31 --> 0.40, bundled SQLite 3.45.0 --> 3.53.2.
    No functional or API changes. Keeps the SQLite dependency on a
    maintained release line so future security fixes can be picked up
    without source changes.
- Update repo lists
---

Version Beta 0.11.4
=====
Update: cmd:slacker search
    - the (also: ...) list now names each repo's own candidate in full,
      e.g. `(also: testing kernel-generic-7.1.7)`, so a repo carrying a
      different version is visible without running `slacker info`.
Update: cmd:slacker status
    - Tag prio: every installed package's source must be ranked or frozen!
      anyway slacker will protect unranked tags and their installed packages
      BUT slacker status will report that this is wrong and user must fix it.
---

Version Beta 0.11.3
=====
Fix bug: slacker search command
- search: label an installed build by its own source, never by the winner
  search_display fell back to the priority winner when no candidate
  matched the installed build tag, so a package installed from a source
  that is not a configured repo (_SBo, _local) was printed as if it came
  from whichever repo happened to outrank it — and with that repo's
  version, which diverges as soon as the versions differ. It now returns
  None for that case and cmd_search labels the line from the installed
  build tag, with the installed name and version. kept_detail shares the
  new installed_source_label helper so both name a source identically.
Update: wiki (for docker & podman)
Add:  contrib/check-yes-noninteractive.sh
Update: Templates folder for docker images.
---

Version Beta 0.11.2
=====
Update: clippy: apply 26 machine-applicable fixes, all tests pass
Add: container folder for testing sbopkg-ci (docker image version)
Add: Vendor folder, start palying with static offline builds...
---

Version Beta 0.11.1
=====
Fix: Bug: `slacker update --yes` or `slacker --yes update` now respect the flag --yes no more questions.
Add: Templates in `/etc/slacker/templates/` these needed when slacker runs in container systems.
Add: minimal/container sackeware64-currnet images (slacker included in image) can be found:
     - https://hub.docker.com/r/rizitis/slackware-slacker
     - https://github.com/rizitis/slackware64-current-ci
---

Version Beta 0.11.0
=====
Add: resolve-stock - pull an official package's STOCK deps on minimal/container systems (only for x86_64)
https://github.com/rizitis/slackware64-current-ci/pkgs/container/slackware64-current-ci

WHAT IT DOES :
Optional, OFF by default (RESOLVE_STOCK=no). When on, install augments an
official package's deps with its stock deps, read from a precomputed sqlite db
(depgraph.db, built by minotavros, fetched from STOCK_DB_URL). The extra deps go
through the SAME plan/prompt path as everything else - shown as `new dep for
<parent>`. slacker still never guesses: it reads a real linked+runtime dep graph,
official packages still ship no auto-dep metadata.

WHY:
A full-ISO Slackware has every stock .so already, so it's a no-op there. But a
minimal/container image (small Docker etc.) is missing them, and stock packages
assume they're present and never declare them. resolve-stock closes that gap
without dragging in a foreign package manager or changing the tradition.

- New module src/stockdb.rs: the edges∪hints query (build-time hints EXCLUDED,
  deduped), db validation, README/ChangeLog freshness stamps. Uses rusqlite with
  the `bundled` feature so sqlite is compiled in - runtime stays glibc-only, no
  system libsqlite3. (5th direct dep, only for this.)
- install: add_with_deps appends the stock deps for official packages, gated
  inside the existing `if resolve` block (--no-deps / RESOLVE_DEPS=no disables it
  too). Missing db --> one warning, continues without stock deps - never a silent
  half-install, never a hard stop.
- update: fetches + validates the db from STOCK_DB_URL on EVERY update (missing or
  stale is always refreshed, even when all repos are up-to-date). Atomic
  temp+rename so a bad download never clobbers a good db. Reports in-sync /
  behind / failed by comparing the source README stamp to the official ChangeLog
  head - never stops the run.
- status: one `Stock-db` row in the Online section (present/valid/in-sync,
  behind, invalid, or "no database installed"). Hidden when the switch is off.

The stock-db is NOT a repo: no PACKAGES.TXT/CHECKSUMS, no priority, never in the
install path. It's a read-only, stock-only source under STATE_DIR
(/var/lib/slacker/stock/depgraph.db, persistent - not the disposable cache).

New conf keys: RESOLVE_STOCK (default no) + STOCK_DB_URL.
With RESOLVE_STOCK off, behaviour is unchanged in every command.

Add: 9 unit tests in stockdb.rs (in-file sqlite, no network/root) - 201 total.
Update: DEV docs (structure.md, CODE_MAP.txt).
Update: Add wiki docker page.
Update: cmd: `slacker status` now also check for mlocate if outdated and inform.
        Fix: AI suggest `re-run with sudo` but in slackware is better to suggest `re-run as root`
---

Version Beta 0.10.3
=====
- Updates: Thanks to @danix !!!
  - New: bash tab-completion for all 38 subcommands. Completes flags,
  installed package names, repo names, @repo / @_tag selectors,
  template names, and pin's `repo:` prefix. Installed by the package
  to /usr/share/bash-completion/completions/slacker and loaded
  automatically in new shells. First external contribution - thanks
  to danix! (PR #3)
  - Completion ignores leftover `-upgraded-<timestamp>` records in
  /var/adm/packages, so an interrupted upgradepkg never produces
  phantom names or garbage tags at the prompt.
  - Developer tooling: contrib/check-completion-drift.sh verifies the
  completion's command list against the live `slacker --help`; the
  SlackBuild now runs it after the tests, so a stale completion
  fails the build instead of shipping. (repo-only, not installed)
  - New: zsh and fish completions alongside bash - all three now
  generated from a single source of truth (contrib/completions.json,
  rendered by contrib/gen-completions.py; python3 at build time only,
  nothing at runtime). Fixes two arg-type bugs of the hand-written
  bash: install-new now completes bare repo names (not @repo), and
  upgrade-all no longer offers selectors (it takes no argument).
  Installed to /usr/share/zsh/site-functions/_slacker and
  /usr/share/fish/vendor_completions.d/slacker.fish. (PR #4)
  - The SlackBuild now also runs gen-completions.py --check, so a
  generated completion that doesn't match its JSON source fails the
  build; together with the drift-check this means completions can
  never silently drift from the binary.
Note: bash requires the bash-completion package (Slackware extra/) for automatic loading - install it with slacker install bash-completion from an extras subtree repo, or source the file from your shell rc. zsh and fish need nothing extra. If you have in use the old style "complete -cf sudo" sudo dont follow correctly you must disable it.
---

Version Beta 0.10.2
=====
Fix: bug arch guard: accept fw and x86 packages, like the available-list filter
 - upgrade | kernel-headers    | 6.18.37-x86-1 -> 6.18.38-x86-1                         | slackware
is valid and should escape fro checks.
Fix: bug in pin: store the pin name verbatim, not as a compiled pattern, thanks to Claude Fable 5
 - dotted/'+' pin names were silently inert
---

Version Beta 0.10.1
=====
Fix: bug for upgrade @repo command, was not correctly filtering pakcage list, thanks to @danix
Update: make upgrade list look more verbose, thanks to @danix
---

Version Beta 0.10.0
=====
Fresh bump release, binaries for current (x86_64 and i686) builded with new shipped rust 1.96.0

Add: Credentials system - zypper-modeled
 - HTTP Basic authentication for repos that require login:
Named sets: /etc/slacker/credentials.d/NAME (username/password), referenced with flag credentials=NAME in repos line.
Global catalogue: /etc/slacker/credentials.cat with [url-prefix] sections.
Order: credentials= flag --> longest catalogue prefix --> anonymous.
Permissions enforced: root-owned 0600, otherwise refuse+warn+anonymous (fail-safe).
Zero leak: secret only in Authorization: Basic header - never in repos file, URL, or logs.
New module credentials.rs with inline base64 (no new dependencies).
https-only + insecure flag (new)
Credentials only go over https (like apt). For http:
add-repo with credentials= on http --> refuse (with clear message).
Explicit alternative: per-repo flag insecure --> sends to http, at your own risk (and vetting no longer freezes it for http, since you accepted it).
The status finds it: new Credentials row (red withheld / yellow insecure).
The list-repos now shows the (credentials=NAME) and (insecure) flags.

Add:  User-Agent: slacker/0.10.0 (rustls) Slackware-version-arch
  - slacker isn not anonymous bot it has id

Fix: Accept-Encoding: identity (fix)
  - All request paths now send explicit identities
Fix: bug with install-new thanks to @conraid
  - now install new will not skip testing/extras/patches/pasture IF having priority higher than slackware repo else keep looking only slackware repo.

Update: cosmetic fix: add space between install-new,installs, new-config headers
Update: slacker new-config command to escape blocking if a mirror is not set up already as it should be
Update: slacker status command to check slacker cache for forgotten (old, huge) packages
---

Version Beta 0.9.4
=====
freeze-fallback: a frozen candidate is treated as absent

WHAT CHANGES (semantic change to `frozen`):
A blacklist (frozen) rule no longer means "hold this package, never touch it".
It now means "do not take THIS candidate". A frozen candidate is treated as if
its repo did not offer the package at all; resolution then proceeds normally by
priority. A package is "held" (left unchanged) ONLY when EVERY candidate it would
consider is frozen.

This makes the three rule shapes behave as one would expect:

  frozen xf86-.*            (unscoped)  -> matches the candidate in EVERY repo,
                                          so all are frozen -> package held
                                          everywhere (hard freeze, as before).
  frozen "@testing xf86-.*" (repo)      -> freezes ONLY the testing candidate ->
                                          resolution falls through to slackware
                                          by priority -> official updates flow.
  frozen "@_SBo foo"        (build tag) -> freezes the _SBo build wherever served;
                                          @scope now matches a build tag too.

A `pin repo:name` still wins: it restricts the candidate set FIRST, then the
freeze excludes within it (so a pinned-but-frozen candidate is held).

The priority invariant is preserved: the fallback only considers candidates whose
priority is >= the installed source's priority (the existing direction rule), so
it never silently downgrades or migrates to a lower-priority repo.

WHY (reported by conraid):
conraid runs `testing` ABOVE `slackware` (105 > 100) and wants the new xf86/Xlibre
testing snapshots frozen while still getting official updates. Under the old
"hold the package" semantics that was impossible: freezing the testing winner left
the package stuck at the installed version with no fallback. Now `@testing xf86-.*`
(or the date rule `xf86-.*-202.*`) freezes only the testing build and slackware's
official update flows.

IMPLEMENTATION:
- repo.rs: AvailPkg gains `frozen: bool`.
- pkgdb.rs: `mark_frozen` sets it once on load (`blacklist_hit` per candidate;
  pins are never frozen). New `resolve_unfrozen` = highest-priority non-frozen
  candidate. `match_pattern` / `search` winner-selection prefers non-frozen, then
  priority. `upgrades_for` uses `resolve_unfrozen` and returns `(ups, held)`.
- pkgdb.rs: `installed_priority` now EXCLUDES frozen candidates from the floor.
  This is essential: a tagless package installed from slackware (100) is ALSO
  served tagless by the higher-priority testing subtree (105); without excluding
  the frozen testing candidate the floor would read 105 and the slackware
  fallback (100) would look like a downgrade and be refused. (This was caught by
  the scoped-fallback test - it is the crux that makes conraid's real case work.)
- config.rs: a `@scope` blacklist rule matches the candidate's REPO name OR its
  build TAG, enabling `@_SBo`, `@cf`, etc.
- main.rs: candidate freeze checks read the precomputed `p.frozen`; `upgrade-all`
  consumes `(ups, held)` and reports held via `note_frozen_excluded`;
  install-template falls through too. Dead `bl_frozen`/`bl_avail` removed;
  `bl_installed` kept for remove / clean-system / remove-template (no candidate
  there to fall through to). upgrade-dist is unchanged (it deliberately bypasses
  the blacklist).

Fix: file-search
- marks only the exact build as installed (not every build of the same name)
Add: pinnded repo:pkg are not frozen it only means give me updates for this pkg ONLY from the repo is pinned, but user might want to keep pkg on clean-system command
- add question and let user to decide, keep or remove ONLY if pkg is installed from the pinned repo.

Update: man.8
---

Version Beta 0.9.3
=====
Fix: bug in cmd_upgrade_all , thanks to conraid again!
- THE BUG (reported live by conraid, reproduced on thinkstar1)
------------------------------------------------------------
`upgrade-all` filtered frozen packages by testing the blacklist against the
INSTALLED id only (bl_installed on u.installed). A date/version rule such as
`xf86-.*-202.*` only ever matches the INCOMING build (e.g.
xf86-input-evdev-20260421_...), never the older installed one (2.11.0), so the
very build the user froze was offered for upgrade. Meanwhile `info` (which tests
bl_frozen on each candidate) correctly showed it [blacklisted] - the visible
inconsistency.

THE FIX (src/main.rs, cmd_upgrade_all)
--------------------------------------
Filter with bl_frozen(cfg, &db, &installed, u.available) - the candidate-aware
check every other path already uses (upgrade <pattern>, install, install-new,
reinstall, info, add_with_deps). It covers both the candidate and any
@repo-scoped rule on the installed source, so nothing the old installed-only
test caught is lost. Frozen names are now collected and reported via
note_frozen_excluded(), so the user sees "frozen (skipped)" instead of a silent
drop. One change, one function. No behaviour change for remove/clean-system
(those correctly stay installed-only - there is no candidate in a removal).
---

Version Beta 0.9.2
=====
This release is "stable enough", in a regular developing tree should be RC.

Update: wiki, add auto translations
- wiki translations was 100% AI generated, if you see something really stupid there please inform me.
Add: slacker banner
---

Version Beta 0.9.1
=====
Fix: typo in doinst.sh
Update: Wiki, man pages,DEV/docs*
Fix: several bugs for glob and regex
Update: some cosmetic fixes...
Update: GPG keys under CACHE_DIR/repos" stale (keyring is STATE_DIR now).
---

Version Beta 0.9.0
=====
Add: slacker now builds and run for i686 systems.
Add: protection mechanism when the wrong repos are activated on the wrong system. example in x86_64 system --> i686 repo or in stable system --> curent repo, of course if someone wants to commit suicide they always find a way...
---

Version Beta 0.8.2
=====
Update: Wiki, man pages
Update: find-mirror now works on -current AND stable (and 32-bit)
Add: cdm: slacker pri-repo 65 repo_name (change priority to 65)
Add: banner.rs
Fix: varius bugs
Fix: bug in Multi-match chooser
Update: Wiki
Update: man pages
Add: cmd slacker pin / unpin - permanent "positive" pin (the opposite of freeze)
- Save INSIDE the blacklist with @repo 100% pkgname syntax (no new files).
- Commands: pin repo:package and unpin package (unpin with no argument = list).
- Semantics: a pinned package is derived ONLY from the pinned repo, ignoring
priority, in ALL commands (incl. upgrade-all). A package has at most one
pin (re-pin = replace). thanks to my dear friend and real life neighbor @gcosbug ;)
Message:
- Hopefully next release will be 0.9.0 with full i686 support and binary AND no more new feature will be be add in slacker please!!! (it ιs not zypper :D)
---

Version Beta 0.8.1
=====
Fix: Bug, Command `slacker status` is read-only, runs "as any user and even in broken config" is not allowed to die with exit 1 because an optional file (distro-upgrade.conf) is not read.
---

Version Beta 0.8.0
=====
Update: wiki
New: add cmd: upgrade-dist (upgrade slackware installation from stable to new stable or current but downgrade)
New: add distro-upgrade.conf file
Update: Cargo.toml file, Slacker stop using native-tls / system OpenSSL
Add: Release status security table (Do not install packages from 3rd repos when release-mismatch)
---

Version Beta 0.7.2
=====
New: add cmd: slacker find-mirror - it find a VALID and fast mirror according to your location.
New: add Freshness in status command that check if your mirror is in sync with upstream (osuosl.org)
New: add cmd: slacker unfrozen <pkg-*>
New: add cmd: slacker revert-pkg <pkg_name> (only for slackware-current) using slackware.uk/cumulative as repo hardcoded
Update: add parallel downloads
Update: cross-repo dep-diff on also: note (install + install-new), read-only, gated on deps-on.
Update: wiki pages
---

Version Beta 0.7.1
=====
Update: man pages
Update: slacker status, complete set of health checks added.(Unix integrity-audit)
Fix: Search label fix (the "B") when a package is installed, search shows the actual installed source (via build tag), not the priority-winner.
Update: Search hint (also: repo) the search (a winner/name) now shows that it exists elsewhere.
Update: Alternatives note (show_plan_alternatives) after plan, before Proceed: shows other repos that give the same name (chosen winner + also...). In install and install-new.
Update: add [q]uit to protected-deps prompt (KeepChoice::Quit)
Bug fix: installed_priority (pkgdb.rs from_pkg
Bug fix: Series detection (pkgdb.rs is_real_series
Fix: Pin-aware priority fix in collect() (the shared install/download/install-new path)
Update: Package selection ([y/N/s] / ("Enter numbers") in the auto-computed sets (upgrade-all, install-new, clean-system, remove-template)
Update: install-new - rewritten
---

Version Beta.3 0.7.0
=====
Major Release Updates.
BREAKING CHANGE: please update your conf file <slacker new-config>
Update: new syntax in repos file: mirror/<subpath>
Add: slacker history
slacker history --help
Show a chronological log of package changes - installed, upgraded and removed, and when - newest first. Derived from the pkgtools admin directories, so it also reflects changes made outside slacker

Usage: slacker history [OPTIONS] [NAME]

Arguments:
  [NAME]  Limit to a single package name

Options:
      --config-dir <CONFIG_DIR>  Directory holding the plain-text config files [default: /etc/slacker]
      --last <LAST>              Show only the most recent N events
      --since <SINCE>            Show only events on or after this date (YYYY-MM-DD)
  -y, --yes                      Assume "yes" to confirmation prompts
      --dry-run                  Show what would happen without changing the system
      --installed                Show only packages currently installed (with their install date)
      --no-deps                  Do not read .dep files / pull in dependencies for this run
      --removed                  Show only packages that left the system (removed or upgraded away)
      --upgraded                 Show only upgrade / reinstall events
  -h, --help                     Print help
---

Version Beta.2 0.6.0
=====
Add: protection mechanism from "rogue" or tampered repositories will be put into auto-quarantine:
slacker {trust-repo,distrust-repo,vet-repo}
Add: slacker status
Add: slacker list-repos + installed counts per repo
Add: slacker add-repo
Add: slacker del-repo
Add: slacker add-tag
Add: slacker del-tag
Add: option immutable a repo
Fix: bug with staled changelogs on 3rd repos
Fix: bug in install-new
Fix: bug with testing,extras,patches,pasture url`s
NEW: slacker clean-system will remove all packages that not exist in slackware PACKAGES.TXT
(excluded blacklisted packages, @repo packages and _tags in /etc/slacker.conf) This way will also be removed
packages that distro official remove.
NOTE: packages from testing extras must be mentioned in blacklist.
---