XPackager 1.5.0 — packages a third smaller, applications to quit, generated uninstallers
XPackager builds signed, notarized and stapled .pkg installers from a project you set up in
a window, without writing pkgbuild or productbuild by hand. It is written in Xojo, on top
of VDSTools. 1.5.0 is out now:
· download
· changelog
· guide
macOS 15 and later. Donation-ware.
Packages are a third smaller. pkgbuild --compression latest, on by default: XPackager’s
own package went from 22.0 to 15.1 MB for identical contents, payloads in pbzx rather than
gzip. If you call pkgbuild yourself, the catch is that the flag requires
--min-os-version and errors out without it instead of falling back — so XPackager compresses
only when your project declares a minimum macOS version, and leaves it alone otherwise rather
than failing your build.
An uninstall script, generated from the receipts. macOS ships no uninstaller, but it keeps
an exact record of what every package laid down. File ▸ Generate an uninstaller script… writes
a .sh to ship with your installer: it reads the receipts, removes files and symlinks, then
directories only if they end up empty, and forgets the receipt. Two traps I only found by
measuring: pkgutil --only-files leaves symlinks out of its listing — so a framework’s
symlinks survive and block every rmdir, and the whole bundle stays behind — and a receipt
from a home-folder install is invisible to pkgutil without --volume "$HOME".
Applications to quit. Per component, a list of bundle identifiers the Installer asks to
close before installing: the answer to replacing a running application. The picker reads the
identifier out of the .app you point at, so you do not have to know it.
Apple’s rejections in plain words. notarytool log is digested rather than dumped as JSON:
the reason in one sentence, then each issue with its locations and Apple’s doc link, identical
issues grouped — Apple repeats the same sentence for every binary and every architecture, which
turns a single fault into a couple of hundred lines.
Downloads are quarantined, and the detail pane scrolls: the window minimum drops from
780 to 600 points, so the pages stay reachable on a scaled-up display or in a half-screen
window.
That quarantine item came out of this thread, and the credit goes to Arnaud Nicolet. The 1.4.0
notes presented XPackager’s own signature check as the only available safeguard, which was
wrong: setting the flag costs nothing and lets macOS do its work, XProtect analysis included.
Jared Feder’s objection — that quarantine would break built-in updaters — holds for an updater
that replaces an .app in place with a downloaded bundle. It does not apply here: the flag
does not propagate through a .pkg, because installd extracts as root without copying
extended attributes, so an application installed from a package is never quarantined. I
measured it. XPackager marks only the package it downloads, and that is the file macOS then
examines if you open it from the Finder.
Next on the list: importing Packages .pkgproj files. Problems and suggestions here, or support@vdsc.fr.