Project

fpm

5.31
There's a lot of open issues
No release in over a year
fpmjordansissel/fpmHomepageDocumentationSource CodeBug TrackerWiki
Convert directories, rpms, python eggs, rubygems, and more to rpms, debs, solaris packages and more. Win at package management without wasting pointless hours debugging bad rpm specs!
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
44,876,941
Stars
11,169
Forks
1,044
Watchers
236
 Releases
Current version
1.15.1
Total releases
129
First release
2011-01-03
Latest release
2023-02-01
 Issues
Open Issues
690
Closed Issues
584
Total Issues
1,274
Issue Closure Rate
45%
 Pull Requests
Open Pull Requests
91
Closed Pull Requests
155
Merged Pull Requests
552
Pull Request Acceptance Rate
69%
 Development
Primary Language
Ruby
Licenses
MIT-like
Average date of last 50 commits
2023-02-12
Reverse Dependencies
34

 Dependencies

Development

insist
~> 1.0.0
pry
>= 0
rspec
~> 3.0.0
rake
>= 0

Runtime

backports
>= 2.6.2
cabin
>= 0.6.0
clamp
~> 1.0.0
pleaserun
~> 0.0.29
stud
>= 0
arr-pm
~> 0.0.11
rexml
>= 0
 Project Readme

fpm

Chat Gem

The goal of fpm is to make it easy and quick to build packages such as rpms, debs, OSX packages, etc.

fpm, as a project, exists to help you build packages, therefore:

  • If fpm is not helping you make packages easily, then there is a bug in fpm.
  • If you are having a bad time with fpm, then there is a bug in fpm.
  • If the documentation is confusing, then this is a bug in fpm.

If there is a bug in fpm, then we can work together to fix it. If you wish to report a bug/problem/whatever, I welcome you to do on the project issue tracker.

You can find out how to use fpm in the documentation.

You can learn how to install fpm on your platform in the installation guide.

Project Principles

  • Community: If a newbie has a bad time, it's a bug.
  • Engineering: Make it work, then make it right, then make it fast.
  • Capabilities: If it doesn't do a thing today, we can make it do it tomorrow.

Backstory

Sometimes packaging is done wrong (because you can't do it right for all situations), but small tweaks can fix it.

And sometimes, there isn't a package available for the tool you need.

And sometimes if you ask "How do I get python 3.9 on RHEL 8?" some unhelpful trolls will tell you to "Use another distro"

Further, job switches have me flipping between Ubuntu and CentOS. These use two totally different package systems with completely different packaging policies and support tools. Learning both was painful and confusing. I want to save myself (and you) that pain in the future.

It should be easy to say "here's my install dir and here's some dependencies; please make a package"

The Solution - FPM

I wanted a simple way to create packages without needing to memorize too much.

I wanted a tool to help me deliver software with minimal steps or training.

The goal of FPM is to be able to easily build platform-native packages.

With fpm, you can do many things, including:

  • Creating packages easily (deb, rpm, freebsd, etc)
  • Tweaking existing packages (removing files, changing metadata/dependencies)
  • Stripping pre/post/maintainer scripts from packages

Things that should work

Sources:

  • gem (even autodownloaded for you)
  • python modules (autodownload for you)
  • pear (also downloads for you)
  • directories
  • tar(.gz) archives
  • rpm
  • deb
  • node packages (npm)
  • pacman (ArchLinux) packages

Targets:

  • deb
  • rpm
  • solaris
  • freebsd
  • tar
  • directories
  • Mac OS X .pkg files (osxpkg)
  • pacman (ArchLinux) packages