jimjag/epm v5.1.0

ESP Package Manager (EPM) - Version 5.1.0

on GitHub

Changes in EPM 5.1.0

• File ownership (user/group in a list file entry) now falls back to a literal numeric ID when no matching account exists on the build system, instead of silently defaulting to root. Fixes Debian/Ubuntu builds where the target uid/gid has no local passwd/group entry (#17); the same fix applies to every backend that resolves ownership (deb, bsd, setld, slackware, aix, macos, and the portable tar backend)
• FreeBSD: -f bsd/-f native now build with pkg(8) via a generated UCL manifest and packing list when /usr/sbin/pkg is present, since pkg_create(8) no longer exists on current FreeBSD releases (#14). Falls back to the legacy pkg_create invocation otherwise; OpenBSD and NetBSD are unaffected. Pre-install and post-remove commands are not yet supported through this path, matching the existing BSD-backend limitation for those two phases
• macOS: the macos-signed format can now apply Developer ID Application signing. Setting EPM_APPLICATION_IDENTITY signs the Mach-O files and .app/.framework/.bundle directories in the package payload with the hardened runtime, then signs the disk image; EPM_SIGNING_ENTITLEMENTS supplies an optional entitlements plist. Setting EPM_NOTARY_KEYCHAIN_PROFILE additionally submits the disk image to the Apple notary service and staples the ticket. Behavior is unchanged when EPM_APPLICATION_IDENTITY is unset
• macOS: a failing pkgbuild is now reported and aborts the build instead of being silently ignored
• macOS: -f macos, -f macos-signed and -f portable now quote the paths they hand to pkgbuild(1), codesign(1) and hdiutil(1). A build whose --output-dir contained a space previously failed outright with "Unable to build package" or "Unable to create disk image", and a signing identity containing an apostrophe was split into two arguments
• BSD: the @exec commands that apply directory ownership in a generated packing list now escape whitespace and shell metacharacters in the path. Those commands run as root at install time, so such a path was previously reparsed by the install-time shell

Full Changelog: v5.0.1...v5.1.0