epm(1)

✨ NAME ✨

hi bestie 💖 meet epm(1) — and it does exactly one thing and does it gorgeously: it creates software packages. That's the whole vibe. This one's credited to Jim Jagielski, and it's part of the ESP Package Manager family. slay. 💅

---

✨ SYNOPSIS ✨

epm [ -a architecture ] [ -f format ] [ -g ] [ -k ] [ -m name ] [ -n[mrs] ] [ -s setup.ext ] [ --depend ] [ --help ] [ --keep-files ] [ --output-dir directory ] [ --setup-image setup.ext ] [ --setup-program /foo/bar/setup ] [ --setup-types setup.types ] [ --uninstall-program /foo/bar/uninst ] [ -v ] [ name=value name=value ] product [ listfile ]

like, yes, that's a lot of brackets. she contains multitudes. 🎀

---

✨ DESCRIPTION ✨

okay so the tea ☕: epm(1) generates software packages — and not just the bare package, it comes complete with installation, removal, and (if necessary) patch scripts too. it's giving whole-package, full-service, main character energy 👑

and unless you've said otherwise, the files it needs for product are read from a file named "product.list". no cap, that's just the default. 🌸

---

✨ OPTIONS ✨

The following options are recognized:

• -a architecture — tells it the actual architecture for the software. skip this one and it'll just use the generic processor architecture instead ("intel", "sparc", "mips", etc.). lowkey convenient, highkey sometimes wrong. 🙈
• -f bsd — generates a BSD distribution, suitable for installing on a FreeBSD, NetBSD, or OpenBSD system. 🦋
• -f deb — generates a Debian distribution, suitable for installing on a Debian-based Linux system. 🍓
• -f native — generates a native distribution. it picks deb or rpm for Linux, bsd for FreeBSD, NetBSD, and OpenBSD, and macos for macOS. everything else defaults to the portable format. it's the "you know what I want" option ✨
• -f macos — (this one's listed here with nothing under it, because the next entry does the talking 👇)
• -f macos-signed — generates a macOS software package. the macos-signed format uses the signing identity from the EPM_SIGNING_IDENTITY environment variable. 🔥
• -f portable — generates a portable distribution built on shell scripts and tar files. the resulting distribution gets installed and removed the exact same way on every operating system. this is the default [default]. bestie-level consistency, we love to see it 🫶
• -f rpm — (again, listed bare, because its signed sibling right below carries the description 👇)
• -f rpm-signed — generates a Red Hat Package Manager ("RPM") distribution, suitable for installing on an RPM-based Linux system. the rpm-signed format uses the GPG private key you've defined in the ~/.rpmmacros file. 🔑
• -g — disable stripping of executable files in the distribution. so they keep all their bits, diva behavior, respect 💅
• -k — keep the intermediate files (spec, etc.) used to create the distribution, right there in the distribution directory. messy but honest 🎀
• -m name — specifies the platform name as a string. the default is to use the auto-generated name that comes from the -n option. ✨
• -n[mrs] — specifies what operating system and machine info gets baked into the package name. distributions are normally named "product-version-system-release-machine.ext", and "product-version-system-release-machine-patch.ext" for patch distributions. that "system-release-machine" chunk can be customized or eliminated with the appropriate trailing letters:
  • all on its own, -n removes the "system-release-machine" string from the filename entirely.
  • the letter m includes the architecture (machine).
  • the letter r includes the operating system version (release).
  • the letter s includes the operating system name.
• -v — increases the amount of information that is reported. stack multiple v's for more verbose output. 📢
• --depend — lists the dependent (source) files for all files in the package. 🧚
• --output-dir directory — specifies the directory for output files. the default directory is based on the operating system, version, and architecture. 📁
• -s setup.ext — (paired with --setup-image below 👇)
• --setup-image setup.ext — includes the ESP Software Wizard with the specified image file, bundled with the distribution. heads up though: this option is currently only supported by portable distributions. 😭
• --setup-program /foo/bar/setup — specifies the setup executable to use with the distribution. and again: this option is currently only supported by portable distributions. 🫶
• --setup-types setup.types — specifies the setup.types file to include with the distribution. yep, you guessed it: this option is currently only supported by portable distributions. 🌈
• --uninstall-program /foo/bar/uninst — specifies the uninst executable to use with the distribution. and (say it with me) this option is currently only supported by portable distributions. 💖

ok real talk bestie: for -s / --setup-image / --setup-program / --setup-types / --uninstall-program, those only play nice with portable distributions. don't come for me, I'm just the messenger 🫠

---

✨ ENVIRONMENT ✨

The following environment variables are supported by epm:

• EPM_SIGNING_IDENTITY — the common name that should be used when signing a package. 🖊️✨

---

✨ LIST FILES ✨

the EPM list file format is now described over in the epm.list(5) man page. so like, go read that one next, it's the sequel 🦋

---

✨ SEE ALSO ✨

epminstall(1), mkepmlist(1), epm.list(5), setup(1).

the friend group 💜

---

✨ COPYRIGHT ✨

Copyright © 1999-2020 by Michael R Sweet, All Rights Reserved. Copyright © 2020 by Jim Jagielski, All Rights Reserved.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

---

and that's the whole page, bestie 💅 this one's from the ESP Package Manager on 20 November 2020 — go make something iconic with it. mwah 🎀💖