{
  "name": "BerryCore",
  "icon": "https://bb10repo.whytofly.de/img/bb10-berrycore.png",
  "category": "Runtime",
  "type": "cli",
  "author": "sw7ft — continuation of Berry Much OS",
  "homepage": "https://berrystore.sw7ft.com/",
  "source": "https://github.com/sw7ft/BerryCore",
  "description": "Meta-package that installs SW7FT's BerryCore extended QNX userland on first install. The package itself contains nothing but a marker file; the post-install hook curls the latest BerryCore install.sh from GitHub Releases and runs it non-interactively, accepting defaults (installs to /accounts/1000/shared/misc/berrycore).\n\nWe ship it this way because BerryCore's GitHub repo has no LICENSE file declared, so we can't legally re-host their compiled binaries in our repo. Going through their official installer keeps the trust chain on sw7ft's side and always gets the latest release.\n\nWhat you get after install: qpkg (BerryCore's own package manager), plus binaries for nano, vim, git, python3, curl, nmap, hydra, ELinks, and dozens of other ports. Open Term49 and they're in your PATH.\n\nAll files land owned by the Term49 / apps perimeter user, so you can modify or update them from Term49 without needing root.",
  "history": [
    {
      "version": "0.77",
      "released": "2026-05-29",
      "changes": "- apk pkgver now tracks the upstream GitHub tag (was a date stamp). Bumping this requires a one-time `apk del bb10-berrycore && apk add bb10-berrycore` on devices with the old dated version, because apk's numeric version comparison treats e.g. 20260526 as greater than 0.77.\n- Installer now pins to a specific tag instead of fetching latest, so the apk version label always matches what's actually on disk."
    },
    {
      "version": "20260526",
      "released": "2026-05-26",
      "changes": "- Initial wrapper package — post-install fetched sw7ft/BerryCore/releases/latest and ran upstream install.sh with default answers."
    }
  ]
}
