SPB Git

Repository Public

distribution.md 9.1 KB

# Distribution

How the signed application becomes downloadable artifacts, where the source lives, and which steps are deliberately not automated because they need the owner's authorization.

Chain: signing → notarization → this document. Gates: release checklist.

State on 2026-11-21: a signed Release bundle, dist/ORIX Sheet.app, was produced by Scripts/sign.sh: universal (x86_64 arm64), Developer ID Application, hardened runtime, no get-task-allow, with the orix-sheet command-line tool embedded at Contents/MacOS/orix-sheet and libduckdb.dylib in Contents/Frameworks, both re-signed (details in signing). The record of the release run — notarization, stapling, artifact sizes, checksums and the Gatekeeper assessments — is RELEASE-REPORT.md at the repository root; this document describes the mechanism and does not repeat those results.

# Artifacts

Artifact Built by Content
dist/ORIX Sheet.app Scripts/sign.sh universal app, Developer ID, hardened runtime; contains the orix-sheet tool (Contents/MacOS/orix-sheet) and Contents/Frameworks/libduckdb.dylib
dist/ORIXSheet-<version>.zip Scripts/package.sh ditto -c -k --keepParent archive of the app
dist/ORIXSheet-<version>.dmg Scripts/package.sh compressed disk image with the app and an Applications link, signed
dist/ORIXSheet-<version>.sha256 Scripts/notarize.sh shasum -a 256 of the DMG and the ZIP

Source: Scripts/package.sh, Scripts/notarize.sh.

<version> is CFBundleShortVersionString read from the app's Info.plist (1.0.0 in project.yml). The build number is not part of the file name. dist/ and build/ are ignored by git: artifacts are never committed.

# Scripts/package.sh

bash
Scripts/package.sh        # normally called by Scripts/notarize.sh after the app is stapled
  1. Stops if dist/ORIX Sheet.app is missing.

  2. Reads the version; removes any previous DMG and ZIP of that version.

  3. ZIP: ditto -c -k --keepParent "dist/ORIX Sheet.app" "dist/ORIXSheet-<version>.zip". ditto preserves the bundle's extended attributes and symbolic links, which a plain zip does not.

  4. Background: uses design/dmg/background.png; if the file is missing it is regenerated with swift design/dmg/make-background.swift design/dmg.

  5. DMG, preferred path: if create-dmg is installed, it is called with:

    Option Value
    Volume name ORIX Sheet <version>
    Window position 200, 140; size 660 × 420
    Icon size 112
    App icon position 170, 205
    Applications drop link 490, 205
    Other --hide-extension "ORIX Sheet.app", --no-internet-enable

    Source: Scripts/package.sh.

    Its output is discarded and its failure is tolerated (>/dev/null 2>&1 || true).

  6. DMG, fallback: if no DMG exists after step 5, the script prints create-dmg unavailable or failed: building a plain disk image, adds an /Applications symlink to the staging directory and runs hdiutil create -format UDZO. This image has no background and no icon layout.

  7. Signing the DMG: the identity is read back from the app's own signature (the Authority=Developer ID Application: … line of codesign -dvv). If found, the DMG is signed with codesign --force --timestamp. If the app is not Developer ID-signed, the DMG is left unsigned without an error.

  8. Prints the size and path of both files.

create-dmg 1.3.0 is installed on the build machine (/opt/homebrew/bin/create-dmg, observed 2026-11-21). create-dmg arranges the window through Finder scripting, so the preferred path needs a logged-in graphical session; on a headless run the fallback applies.

Two details worth knowing:

  • The header comment of package.sh describes the ZIP as "the signed, stapled app". That is true only when the script is called from notarize.sh after stapling. Run on its own after sign.sh, it archives an app without a ticket.
  • The staging copy is made in a mktemp -d directory and removed at the end; on an error under set -e it is left behind in the temporary directory.

# Disk-image artwork

design/dmg/make-background.swift (33 lines, AppKit/CoreGraphics) draws design/dmg/background.png:

Property Value
Pixel size 1320 × 840 (the 660 × 420 pt window at 2x; the PNG is tagged 660 × 420 pt)
Background vertical gradient #16233F → #0B0F1E, radial glow #1E6A8A at 55 % from the top-left
Grid faint sheet grid, white at 3.5 %, every 110 px horizontally and 56 px vertically
Arrow cyan #22D3EE at 90 %, between the two icon positions (y = 205 pt)
Text "ORIX Sheet" (56 px bold, white), "Beyond Spreadsheets." (26 px medium, cyan), "Drag ORIX Sheet to the Applications folder" (26 px, white at 72 %)

Source: design/dmg/make-background.swift; pixel size confirmed with sips (file size 886,139 bytes).

The text of the background is English only. The icon positions in package.sh and the arrow coordinates in the generator are two independent literals: change them together.

# Verifying a download

bash
cd dist && shasum -a 256 -c ORIXSheet-1.0.0.sha256
xcrun stapler validate ORIXSheet-1.0.0.dmg
spctl --assess --type open --context context:primary-signature --verbose=2 ORIXSheet-1.0.0.dmg

The checksum file is produced next to the artifacts and proves integrity only against an accidental change; it is not signed separately. Authenticity comes from the Developer ID signature and the notarization ticket.

# Where the source lives

Fact Value Observed with
Remote origin (fetch and push) gitsrv:srv/git-private/orix-sheet.git git remote -v
Branch main, tracking origin/main git status -sb
Last commit on 2026-11-21 1a190fd ("release: 1.0.0 (1) signed, notarized and packaged; release report, facts and badges") git log --oneline -1
Bare repository on the host srv/git-private/orix-sheet.git exists; srv/git/orix-sheet.git does not ssh gitsrv ls -d … (read-only)
Files tracked 1,071 git ls-files | wc -l
Tags v1.0.0-build1 git tag

Source: read-only git and ssh commands run on 2026-11-21. gitsrv is an SSH host alias defined in the developer's SSH configuration, not in this repository.

Why a path outside the forge: the SPB Git forge serves the bare repositories under srv/git/, and it has no notion of a private repository — everything in that directory is publicly listed. ORIX Sheet's source is not meant to be public, so its bare repository sits in a sibling directory, srv/git-private/, on the same host, reachable only over SSH with the developer's key. The listing above confirms the location; that the forge does not expose srv/git-private/ is a property of the forge's configuration, which this repository does not contain and this document did not test.

Consequences:

  • There is no web page, issue tracker or release page for ORIX Sheet on the forge. Nothing in the repository publishes an artifact anywhere.
  • Access to the source is by SSH to that host; cloning needs an authorized key.
  • Third-party binaries are not in git: DuckDB is downloaded by Scripts/fetch-duckdb.sh from the project's GitHub release (v2.0.1, pinned SHA-256) on the first build. A fresh clone therefore needs network access once.

# Steps that require the owner's authorization

None of the following is performed by a script without an explicit command from the owner. Whether each was performed for a given release is recorded in RELEASE-REPORT.md, not here:

Step Why it needs the owner
Scripts/notarize.sh uploads the application to Apple under the owner's developer account (keychain profile MacLustr-Notarize by default)
git push to origin publishes commits to the private repository; Scripts/secret-scan.sh is to be run first
Making any artifact downloadable (a release page, a website link, sending the DMG to someone) no public location exists for this project; choosing one is a product decision. If a public forge repository were created for releases, it would be public in full
Tagging a release one tag exists, v1.0.0-build1 (git tag); creating or moving a tag is the owner's decision
An update feed Sparkle 2 is "the candidate" but "not included in 1.0": it needs a hosted, signed appcast and a key-management decision (docs/research/technology-evaluation.md). The app has no updater and performs no update check
Mac App Store submission not prepared: the app is not sandboxed and has no App Store configuration

Source: Scripts/notarize.sh, Scripts/secret-scan.sh, docs/research/technology-evaluation.md, project.yml.

# Not implemented

  • No automatic upload, no release notes generator, no appcast, no licence or EULA shown in the DMG.
  • No separate arm64-only artifact: the Release configuration is universal (arm64 x86_64).
  • No dSYM archive is kept by the scripts.
  • RELEASE-REPORT.md is the record of the actual release run and takes precedence over this document for results (notarization, checksums, Gatekeeper).
Files main
Menu

Theme