fix metadata naming, add shellcheck requirement, remove bincache/pkgcache separation

Author: QaidVoid

about.md

@@ -43,9 +43,8 @@ The main package repository with 500+ SBUILD recipes, automated CI builds, and m
 
 - **July 2023**: [Toolpacks](https://github.com/Azathothas/Toolpacks) created — scripts for fetching precompiled binaries
 - **Nov 2023**: [Hysp](https://github.com/pwnwriter/hysp), the first package manager for Toolpacks
-- **Sep 2024**: pkgcache created for portable package formats (AppImage, FlatImage, etc.)
 - **Oct 2024**: [Soar](https://github.com/pkgforge/soar) receives its first commit
-- **Nov 2024**: [PkgForge](https://github.com/pkgforge) organization created, soarpkgs unifies bincache + pkgcache
+- **Nov 2024**: [PkgForge](https://github.com/pkgforge) organization created, soarpkgs established
 - **Jan 2025**: Toolpacks archived, fully replaced by soarpkgs
 
 ## Resources

contributing/creating-packages.md

@@ -51,24 +51,18 @@ Key things to remember:
 ## Step 3: Validate
 
 ```bash
-# Install sbuild
-soar install sbuild
+# Install sbuild and shellcheck
+soar install sbuild shellcheck
 
 # Validate your SBUILD
 sbuild lint ./myapp.yaml
-
-# Check YAML syntax
-# Visit: https://www.yamllint.com/
-
-# Check shell syntax
-# Visit: https://www.shellcheck.net/
 ```
 
 ## Step 4: Test Locally
 
 ```bash
 # Run the build
-sbuild ./myapp.yaml
+sbuild build ./myapp.yaml
 ```
 
 ## Step 5: Submit

repositories/custom-repos.md

@@ -39,10 +39,12 @@ soar install sbuild
 
 Or grab them from [sbuilder releases](https://github.com/pkgforge/sbuilder/releases).
 
-Pushing to GHCR requires [oras](https://oras.land/). Install it with:
+Additional requirements:
+- [oras](https://oras.land/) — for pushing packages to GHCR
+- [shellcheck](https://www.shellcheck.net/) — for linting shell scripts in recipes
 
 ```bash
-soar install oras
+soar install oras shellcheck
 ```
 
 ### 2. Build Packages
@@ -90,10 +92,7 @@ This scans your recipe directories, queries GHCR for package info, and produces
 
 ```
 metadata/
-├── bincache/
-│   └── x86_64-linux.json
-└── pkgcache/
-    └── x86_64-linux.json
+└── x86_64-linux.json
 ```
 
 Key `sbuild meta generate` options:
@@ -104,7 +103,6 @@ Key `sbuild meta generate` options:
 | `--recipes` | Recipe directories to scan |
 | `--output` | Output directory for JSON files |
 | `--ghcr-owner` | GHCR owner/organization |
-| `--cache-type` | Generate `bincache`, `pkgcache`, or `all` (default: all) |
 | `--parallel` | Number of parallel workers (default: 4) |
 
 ### 4. Host Metadata

repositories/index.md

@@ -12,8 +12,7 @@ soarpkgs (github.com/pkgforge/soarpkgs)
 │   ├── Publishes to ghcr.io/pkgforge/*
 │   └── Generates metadata
 ├── GitHub Releases
-│   ├── bincache-{arch}.sdb.zstd (static binaries metadata)
-│   ├── pkgcache-{arch}.sdb.zstd (portable packages metadata)
+│   ├── metadata-{arch}-linux.sdb.zstd (package metadata)
 │   └── Minisign signatures
 └── Soar fetches metadata → downloads packages from ghcr.io
 ```
@@ -27,16 +26,13 @@ soarpkgs (github.com/pkgforge/soarpkgs)
 5. Metadata is signed with minisign
 6. Soar downloads metadata → installs packages from ghcr.io
 
-## Metadata Views
+## Metadata
 
-Metadata is split into two views:
+Metadata is published as a compressed SQLite database (`.sdb.zstd`) per architecture:
 
-| View | Contents | URL Pattern |
-|---|---|---|
-| **bincache** | Static binaries | `soarpkgs/releases/.../bincache-{arch}-Linux.sdb.zstd` |
-| **pkgcache** | Portable packages (AppImage, FlatImage, etc.) | `soarpkgs/releases/.../pkgcache-{arch}-Linux.sdb.zstd` |
-
-Format: compressed SQLite database (`.sdb.zstd`)
+```
+soarpkgs/releases/.../metadata-{arch}-linux.sdb.zstd
+```
 
 Supported architectures: `x86_64-Linux`, `aarch64-Linux`, `riscv64-Linux`
 

repositories/metadata.md

@@ -1,22 +1,18 @@
 # Metadata
 
-soarpkgs generates metadata for all prebuilt packages, split into two views:
-
-- **bincache** — static binary metadata
-- **pkgcache** — portable package metadata (AppImage, FlatImage, etc.)
+soarpkgs generates metadata for all prebuilt packages — a single metadata file per architecture.
 
 ## URLs
 
 Metadata is available in JSON and SQLite formats:
 
 ```
-https://github.com/pkgforge/soarpkgs/releases/latest/download/bincache-${HOST}.json
-https://github.com/pkgforge/soarpkgs/releases/latest/download/pkgcache-${HOST}.json
+https://github.com/pkgforge/soarpkgs/releases/latest/download/metadata-${ARCH}-linux.json.zstd
 ```
 
-Append `.zstd` for compressed versions. SQLite format uses `.sdb` / `.sdb.zstd`.
+Also available as `.json`, `.sdb`, or `.sdb.zstd`.
 
-`${HOST}` is one of: `aarch64-Linux`, `x86_64-Linux`
+`${ARCH}` is one of: `aarch64`, `x86_64`
 
 ## Fields
 
@@ -80,11 +76,11 @@ snapshots: "@array"           // Version tags
 
 ```bash
 # List all packages
-curl -qfsSL "https://github.com/pkgforge/soarpkgs/releases/latest/download/bincache-$(uname -m)-$(uname -s).json" \
+curl -qfsSL "https://github.com/pkgforge/soarpkgs/releases/latest/download/metadata-$(uname -m)-linux.json" \
   | jq -r '.[] | .pkg'
 
 # Search for a package
-curl -qfsSL "https://github.com/pkgforge/soarpkgs/releases/latest/download/bincache-$(uname -m)-$(uname -s).json" \
+curl -qfsSL "https://github.com/pkgforge/soarpkgs/releases/latest/download/metadata-$(uname -m)-linux.json" \
   | jq -r '.[] | select(.pkg | test("qbittorrent"; "i"))'
 ```
 

repositories/soarpkgs.md

@@ -30,12 +30,6 @@ We'll help fix any issues and provide feedback. See [Creating Packages](/contrib
 
 Inspired by the AUR concept but curated — packages are reviewed by maintainers before inclusion.
 
-### What is bincache/pkgcache?
-
-These are metadata views generated from soarpkgs:
-- **bincache**: prebuilt static binaries
-- **pkgcache**: prebuilt portable packages (AppImage, FlatImage, etc.)
-
 ### GLIBC vs MUSL
 
 MUSL binaries use [mimalloc](https://github.com/microsoft/mimalloc) for performance parity with GLIBC. LTO and PIE optimizations are also applied.

sbuild/linting.md

@@ -1,6 +1,14 @@
 # Linting
 
-The `sbuild` tool includes a built-in linter that validates SBUILD recipes before execution. It checks for required fields, correct types, and valid values.
+The `sbuild` tool includes a built-in linter that validates SBUILD recipes before execution. It checks for required fields, correct types, valid values, and runs [shellcheck](https://www.shellcheck.net/) on shell scripts.
+
+## Prerequisites
+
+- [shellcheck](https://www.shellcheck.net/) — used to validate `x_exec.run` and `x_exec.pkgver` blocks
+
+```bash
+soar install shellcheck
+```
 
 ## Installation
 
@@ -19,8 +27,14 @@ sbuild lint ./myapp.yaml
 # Validate multiple files
 sbuild lint ./packages/*.yaml
 
-# Validate with verbose output
-sbuild lint -v ./myapp.yaml
+# Validate in parallel
+sbuild lint -p 8 ./packages/*.yaml
+
+# Run in pkgver mode (execute pkgver scripts)
+sbuild lint -P ./myapp.yaml
+
+# Skip shellcheck validation
+sbuild lint --no-shellcheck ./myapp.yaml
 ```
 
 ## What It Checks
@@ -29,8 +43,8 @@ sbuild lint -v ./myapp.yaml
 - **Field types**: Arrays must be arrays, strings must be strings
 - **Valid values**: `pkg_type` must be a recognized format, `category` must match FreeDesktop spec
 - **Name constraints**: `pkg`, `pkg_id`, `app_id` only allow `[a-zA-Z0-9+\-_.]`
-- **Shell syntax**: Validation of `x_exec.pkgver` and `x_exec.run` blocks via shellcheck
-- **URL format**: `src_url`, `homepage`, and `build_asset.url` entries must be valid URLs
+- **Shell syntax**: Validates `x_exec.pkgver` and `x_exec.run` blocks via shellcheck
+- **URL format**: `src_url`, `homepage` entries must be valid URLs
 - **Host triples**: `x_exec.host` entries must match `{arch}-{os}` format
 
 ## Common Errors
@@ -64,6 +78,4 @@ The `run` block must contain actual shell commands.
 Before submitting an SBUILD to soarpkgs:
 
 1. Run `sbuild lint` — no errors
-2. Check YAML syntax with [yamllint](https://www.yamllint.com/)
-3. Check shell syntax with [ShellCheck](https://www.shellcheck.net/)
-4. Test the build locally with `sbuild`
+2. Test the build locally with `sbuild build`