Recommended Free Tools
Yes. fpm can turn one staged application tree into Debian, RPM, Pacman, Alpine APK and other package formats. The reliable pattern is to define the source once, keep common metadata in a .fpm options file, and invoke fpm once per target format. You still need to inspect and test each generated package because dependency syntax, architecture labels, scripts, compression and repository policy vary by format.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
What fpm does
fpm is a package-building and package-conversion tool. Its basic model has three parts:
As an Amazon Associate I earn from qualifying purchases.
- Source type: where the files or package metadata come from.
- Target type: the package format to create.
- Source inputs: the directory, archive, language package or existing package being converted.
The official Getting Started guide summarizes the model this way: “Given a source and a target, FPM can convert all the source files into a package of the target format.” For a local application, that usually means -s dir for the input and -t deb, -t rpm, -t pacman or -t apk for the output.
fpm does not make Debian, RPM, Arch or Alpine policy identical. It provides handlers for those formats and translates your inputs into each one. Treat the resulting files as separate deliverables: build them from the same source definition, then validate installation, upgrades, removal, dependencies and scripts on every distribution family you support.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
Prepare a clean staging tree
The directory input method is the easiest way to package an application you have already installed into a temporary filesystem tree. Build that tree in a clean workspace so test files, source control directories and developer-only assets cannot be captured accidentally.
mkdir -p pkgroot/usr/bin pkgroot/usr/share/man/man1
install -m 0755 hello-world pkgroot/usr/bin/hello-world
install -m 0644 hello-world.1 pkgroot/usr/share/man/man1/hello-world.1
Each mapping passed to fpm uses the form source=destination. In the example above, the executable is installed as /usr/bin/hello-world and the manual page as /usr/share/man/man1/hello-world.1. You can map files directly without first changing the current directory, but an explicit staging tree is easier to audit and reproduce.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Include only runtime files.
- Set ownership and permissions before building, or specify them through the target-specific options you use.
- Keep configuration files separate from generated state, caches and logs.
- Record the exact source revision used for the build.
Build a Debian package from a directory
This command follows the documented directory-to-Debian workflow:
fpm
-s dir -t deb
-p hello-world-0.1.0-1-any.deb
--name hello-world
--license agpl3
--version 0.1.0
--architecture all
--depends bash --depends lolcat
--description "Say hi!"
--url "https://example.com/hello-world"
--maintainer "You The Amazing Person <[email protected]>"
hello-world=/usr/bin/hello-world
hello-world.1=/usr/share/man/man1/hello-world.1-s dir tells fpm that the inputs are local files. -t deb selects the Debian handler, and -p chooses the output path. The repeated --depends options become runtime dependencies. --architecture all is appropriate for an architecture-independent script; a package containing native binaries needs the architecture value that matches the binaries and the distribution policy.
The package name, version, license, description, project URL and maintainer are not cosmetic fields. Package managers and repositories use them to identify, display, upgrade and audit the package. Set them deliberately rather than relying on defaults.
Emit several formats from the same definition
fpm does not normally write every format in one invocation. Run it once for each target and change the target type and output path:
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
fpm
-s dir -t deb
-p hello-world-0.1.0-1-any.deb
--name hello-world
--version 0.1.0
--architecture all
--depends bash
--description "Say hi!"
--maintainer "You The Amazing Person <[email protected]>"
hello-world=/usr/bin/hello-world
fpm
-s dir -t rpm
-p hello-world-0.1.0-1.x86_64.rpm
--name hello-world
--version 0.1.0
--architecture all
--depends bash
--description "Say hi!"
--maintainer "You The Amazing Person <[email protected]>"
hello-world=/usr/bin/hello-worldThe second filename is only an output-path example. Make its architecture label agree with the metadata and payload you actually build; do not label an architecture-independent script as a native x86_64 package merely because that string appears in a filename.
For Pacman or Alpine, replace the target and extension:
fpm -s dir -t pacman -p hello-world-0.1.0-1-any.pkg.tar.zst ...
fpm -s dir -t apk -p hello-world-0.1.0-r0.apk ...Use the target handler’s accepted metadata and filename conventions. The same file mappings can be reused, but dependency names, release fields, architecture names and script behavior may require target-specific adjustments.
Keep shared options in a .fpm file
Repeating a long command for every format invites drift. Put common settings in a file named .fpm (or another file passed with --fpm-options-file):
-s dir
--name hello-world
--license agpl3
--version 0.1.0
--architecture all
--depends bash
--depends lolcat
--description Say hi!
--url https://example.com/hello-world
--maintainer You The Amazing Person <[email protected]>
hello-world=/usr/bin/hello-world
hello-world.1=/usr/share/man/man1/hello-world.1
With that file in the working directory, the target-specific commands become:
fpm -t deb -p hello-world-0.1.0-1-any.deb
fpm -t rpm -p hello-world-0.1.0-1.x86_64.rpm
fpm -t pacman -p hello-world-0.1.0-1-any.pkg.tar.zst
fpm -t apk -p hello-world-0.1.0-r0.apkCommand-line flags override values loaded from the options file. Keep universal values—file mappings, name, version, license, architecture, dependencies, description, URL and maintainer—in the shared file. Keep format-specific flags on each command line, or maintain separate options files when a target needs different dependency names, release metadata, compression or script settings.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Do not assume that a successful build proves the shared metadata translated correctly. Inspect each package’s metadata independently and compare it with the intended values.
Metadata you should set deliberately
A useful package is more than an archive of files. Before building, decide the following fields for every supported target:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →| Field | Why it matters | fpm controls |
|---|---|---|
| Name | Identifies the package to package managers and upgrade logic. | --name or -n |
| Version | Determines ordering and whether an upgrade is newer than an installed build. | --version or -v |
| Architecture | Controls which machines may install the package. | --architecture or -a |
| Dependencies | Lets the package manager resolve required runtime components. | Repeat --depends or -d |
| Description | Explains the package in local package-manager listings. | --description |
| License | Communicates licensing information to users and repositories. | --license |
| Project URL | Gives maintainers a canonical project location. | --url |
| Maintainer | Provides a contact for packaging and operational issues. | --maintainer |
| Configuration files | Allows package managers to treat user-edited files differently during upgrades and removal. | --config-files |
| Lifecycle scripts | Runs actions before or after installation, upgrade or removal. | --before-install, --after-install, --before-upgrade, --after-upgrade |
Also decide the package iteration or release value used by your target ecosystem. A version such as 0.1.0 may stay constant while you publish packaging-only revisions; those revisions must still be distinguishable to the package manager. Confirm the exact release option and ordering rules for the handler you are using.
Configuration files and lifecycle scripts
Mark files that administrators are expected to edit with --config-files. This gives the target package manager the information needed to preserve local changes or warn about replacements. Do not mark logs, caches or generated state as configuration.
Lifecycle hooks can perform setup and cleanup work, such as creating a service account, refreshing a cache or enabling a service. The current CLI reference documents before- and after-install, before- and after-upgrade, and removal-related script families. Its documented install/remove/upgrade script support covers Debian, RPM and Pacman packages; do not assume the same hooks are available or interpreted identically for APK, tar, zip or other outputs.
- Make scripts idempotent so a retry does not corrupt an installation.
- Use absolute paths and check command failures.
- Do not start network downloads or silently overwrite administrator data.
- Test fresh installation, upgrade, downgrade where supported, and removal.
Package inputs besides a directory
The source type can be changed when your software already exists in another packaging ecosystem.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesRank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
| Input type | Example shape | What fpm does |
|---|---|---|
| NPM | fpm -s npm -t deb package-name |
Obtains package metadata from npm and emits a supported target such as Debian, RPM, Pacman, Solaris, FreeBSD, macOS package or tar. |
| Ruby gem | fpm -s gem -t deb fpm |
Turns a gem into a Debian package; the documented example uses the gem named fpm. |
| Existing Debian, RPM or Pacman package | fpm -s deb -t rpm existing.deb |
Reads an existing package and converts it to another supported target. |
| Python or virtualenv | Use the corresponding input handler and target. | Packages Python application content for a selected output format. |
| CPAN, PEAR or pkgin | Use the package-system input handler. | Converts language or platform package metadata into a target package. |
| Archive or empty package | Use zip, tar or empty-package inputs where appropriate. | Creates a package from an archive or metadata-only definition. |
Supported output families listed in the documentation include Debian, RPM, Solaris, FreeBSD, macOS package, Pacman, Puppet, p5p, shell archive, tar, zip and a directory tree, in addition to Alpine APK support through its dedicated handler. Availability of a particular combination depends on the input and output handlers; check the current CLI reference before building a less common pair.
How targets differ
One options file is useful for shared intent, not proof that every ecosystem has identical semantics. Review these axes for each output:
| Axis | Questions to answer before release |
|---|---|
| Dependency names and versions | Does the target use the same package names? Are version operators and virtual capabilities expressed differently? |
| Configuration handling | Will an edited file be preserved, replaced, or flagged during upgrade? |
| Lifecycle scripts | Which hooks are supported, and in what order do they run on install, upgrade and removal? |
| Ownership and permissions | Do files arrive with the intended user, group, mode and directory ownership? |
| Compression | Does the target’s default compression suit your repository and deployment tooling? |
| Architecture naming | Does the handler expect all, a CPU-specific name, or another platform label? |
| Repository and signing policy | Does your repository require signatures, checksums, a release field or additional metadata? |
For example, a dependency that is called one thing on Debian may have a different name on an RPM-based distribution. Keep target-specific dependency declarations separate when necessary instead of forcing one name into every package.
Reproducible build controls
The CLI reference documents --source-date-epoch-default and --source-date-epoch-from-changelog. These options let you control or derive timestamps so repeated builds are less affected by the current clock. The changelog-based option is described as experimental and is currently implemented for gem input. No published reproducibility rate or benchmark is established by the documentation.
For practical reproducibility:
- Build from a clean, fixed source tree.
- Use a deliberate version and release value.
- Set a source date epoch when your build policy requires stable timestamps.
- Keep generated files and environment-specific paths out of the staging tree.
- Compare package metadata and file lists, not only the output filename.
Validate every generated package
Build artifacts should be tested on the distributions and architectures you actually support. Documentation describes fpm’s options; it does not replace execution tests.
- Inspect metadata. Confirm name, version, release or iteration, architecture, dependencies, description, license, URL and maintainer.
- Inspect the file list. Check paths, modes, ownership and configuration-file declarations. Ensure no build secrets or source-control directories are present.
- Install in a clean virtual machine or container. Verify that dependency resolution succeeds using the native package manager.
- Run the application. Exercise the installed command, service or entry point using the paths in the package.
- Test upgrades. Install the previous package, upgrade to the new one, and verify preserved configuration and expected migration behavior.
- Test removal. Remove the package and check which configuration or generated data should remain under your distribution’s policy.
- Repeat for each target. A passing Debian test does not establish that the RPM, Pacman or APK package has equivalent dependency or script behavior.
Troubleshooting common failures
The package contains unexpected files
Rebuild from a new staging directory and use explicit source-to-destination mappings. Inspect the file list before installation. Do not package an entire development checkout merely because it is convenient.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
A dependency cannot be resolved
Check the target package database for the distribution-specific name and version syntax. Replace a shared dependency declaration with a target-specific one when Debian, RPM, Arch or Alpine names differ.
The package installs but the command is missing
Verify the destination path, executable mode and ownership. If a lifecycle script creates links or directories, run the package’s install test again and inspect script output for a failed command.
An upgrade overwrites a local configuration
Declare the file with --config-files, then test an upgrade with a locally edited copy. Configuration behavior is handled by the target package system, so verify it separately for each output.
A lifecycle hook works in one format but not another
Confirm that the target handler supports the hook family you selected. The documented install, remove and upgrade script support is for deb, rpm and pacman; redesign the package or move the action to deployment tooling when another target does not provide equivalent hooks.
The filename and architecture disagree
Treat the filename as a label, not a substitute for metadata. Set --architecture to match the payload and target convention, then rename the output path to the same convention.
A repeatable multi-format build checklist
- Define the source tree and map every runtime file explicitly.
- Put common fpm options in a version-controlled
.fpmfile. - Choose a deliberate name, version, release or iteration, architecture, license, dependencies, description, URL and maintainer.
- Mark administrator-edited files with
--config-files. - Keep target-specific flags, dependency names and script behavior separate where needed.
- Run one fpm command per output format.
- Inspect metadata and file lists for every artifact.
- Install, upgrade, run and remove each package on its real target distribution.
- Apply your repository’s signing and publication policy after validation.
This approach gives you one maintainable source definition without pretending that package formats are interchangeable. fpm handles the mechanical conversion; your build and test process remains responsible for distribution-specific correctness.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
