rizitis/slacker
2
1
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions
6 releases 6 tags
  • 0.7.0_beta.3 2f5b089b51

    0.7.0_beta.3 Pre-release

    rizitis released this 2026-06-25 01:01:15 +02:00 | 1 commits to main since this release

    Major Release Update: BETA-3

    BREAKING CHANGE: please update your conf files
    Update: new syntax in repos file: mirror/
    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 Show only the most recent N events
    --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

    • A pre-compiled binary for slackware64-current included
    • Please read the new slacker Wiki
    Downloads
  • 0.6.0_beta.2 0618946033

    0.6.0_beta.2 Pre-release

    rizitis released this 2026-06-24 06:32:12 +02:00 | 11 commits to main since this release

    feat!: repo management, subtree/immutable, quarantine; baseline clean-system

    Added: status, list-repos, add/del-repo, add/del-tag, vet/trust/distrust-repo,
    immutable & subtree repo flags, TOFU key pinning, and quarantine. Fixes
    extra/testing/patches/pasture URLs, stale 3rd-party changelogs, install-new.

    BREAKING CHANGE: clean-system now removes packages absent from the official
    baseline (official PACKAGES.TXT + immutable repos), not only those in no repo.
    Set IGNORE_TAGS and/or mark repos immutable before running it.

    NOTE: This release wants to update your /etc/slacker/repos file in order to fix a bug per testing and extra repos and make them usable again.
    After installation finish
    cmd: "slacker config-new" and accept new repos file
    then edit your repos file again BUT dont remove the "subtree" flag after testing url or extras url
    When you are ready with your repo priorities
    cmd: slacker update gpg
    slacker update

    New commands added:
    slacker status
    slacker list-repos
    slacker add-repo
    slacker del-repo
    slacker add-tag
    slacker del-tag

    man slacker slacker --help for more details...
    You also might want to read this docs: https://forge.slackware.nl/rizitis/slacker/src/branch/main/wiki

    Downloads
  • 0.5.2_beta.2 dc93cc5854

    0.5.2_beta.2 Pre-release

    rizitis released this 2026-06-23 21:18:46 +02:00 | 19 commits to main since this release

    Update: This is a blacklist release thanks @conraid
    for more information please read https://forge.slackware.nl/rizitis/slacker/src/branch/main/wiki/blacklist-reference.md (eng)
    and https://forge.slackware.nl/rizitis/slacker/src/branch/main/wiki/blacklist-reference-multilang.md (mulitlang)

    • Italiano
    • Русский
    • Español
    • 中文
    • Français

    NOTE: all docs and man pages updated using AI machine

    Downloads
  • 0.5.0_beta.2 4c77cffa5e

    0.5.0_beta.2 Pre-release

    rizitis released this 2026-06-23 16:29:19 +02:00 | 21 commits to main since this release

    Fixes:
    - Make sure gpg and mdsums checks for all , per repo and per package.
    - Τhe global options (--dry-run, --yes, --no-deps, --config-dir) are entered before the subcommand, now they can be entered after too
    - dependency resolver not to ignore priority and ask what to do with already installed deps from higher priority repos.
    - check for updates only from CHECKSUMS.md5 instead of PACKAGES.TXT. (Much smaller and faster)
    - new-config: colored diff -u, and options [K]eep both (default, zero deletion) / [O]verwrite / [R]emove .new / [M]erge / [D]iff. Identical .new is automatically deleted. No interference with doinst.sh work.Broken package (.new without old): red warning banner, leaves it intact, continues.
    - slacker search exact name, foo only finds foo, not libfoo/foobar (file-search remains as is).
    - Update redesign: Check phase - for each active repo I find status (up-to-date / has changes / new), without full download.Add Status table of all active repos.Select update_repo only in selected ones.

    Add:
    - slacker show-changelog accepts optional name repo. No argument print only the official one (as before)

    Downloads
  • 0.4.1_beta.1 492c9f8edf

    0.4.1_beta.1 Pre-release

    rizitis released this 2026-06-23 00:23:55 +02:00 | 25 commits to main since this release

    Fix: varius bugs

    • special one according to repo and packages priority thanks to @conraid
      Add colors in cli prompts package status and repos
      Add tables when listing packages (update/remove/forezen etc)

    Still on beta.1

    Downloads
  • 0.4.0_beta.1 ed802e4790

    0.4.0_beta.1 Pre-release

    rizitis released this 2026-06-22 17:44:21 +02:00 | 31 commits to main since this release

    First beta release of the package manager.

    This release is intended for testing and feedback only.

    What we'd like you to test

    • Package installation
    • Package removal
    • Package upgrades
    • Dependency resolution (for repos that support it)
    • Repository management
    • Error handling and edge cases

    Feedback

    If you encounter any issues, please open an issue and include:

    • Steps to reproduce
    • Expected behavior
    • Actual behavior
    • Logs or screenshots (if applicable)

    Feature suggestions

    Have an idea that could improve the project?

    Feel free to open a Feature Request or start a Discussion. Whether it's a new feature, a workflow improvement, a usability enhancement, or anything else you'd like to see, we'd love to hear your ideas.

    All suggestions are welcome!

    Thank you for taking the time to test the project and help make it better!

    Downloads