Building native Linux packages for Passenger is now possible
Some people say that they won’t install Passenger until native Linux packages are available.
Well, we’ve made some modifications to Passenger to make packagers’ lives a bit easier:
- There’s now a Rake task called fakeroot. This generates a directory hierarchy in pkg/fakeroot, which can be directly turned into a native package.
- There’s also a package:debian task which generates a Debian package. But this Debian package is very generic. For example, it doesn’t specify any dependencies at all, because:
- Passenger requires fastthread, and Debian doesn’t provide a native package for that.
- Lots of people have Ruby and/or Apache installed from source.
Despite that, our Debian package specification files can be used as a base for packagers who wish to create more distribution-specific packages.

We’re looking for volunteers who wish to maintain packages for their distribution. Packagers should:
- package early, package often. Native packages should follow as soon as possible after a Passenger release. Or – preferably – be released at the same time.
- test early, test often. Packagers should test our development version from time to time to verify that generated packages still work.
- drink beer with us.
Needless to say, the more Linux packages we can put on our website, the better. Please contact us if you’d like to volunteer. Thanks.
Phusion. All rights reserved.
Cheers,
I’m already working on a FreeBSD port.
Seeing the fakeroot task is very nice.
I will vounteer for maintaining a FreeBSD port,
Jonathan
as of ruby 1.8.6.110 you shouldn’t need fastthread. ruby on debian stable is 1.8.2, but on unstable and testing it is 1.8.6.114. the latter is what is going to be used to build the package on debian and derivatives like ubuntu. see http://packages.debian.org/ruby1.8 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472702#32
I’m doing a real Debian package that does do dependencies and ties everything together correctly so that it has a fighting chance of getting in the archives at some point. Is that of interest?
Definitely of interest to me.
Apparently gems and debian don’t mix well:
http://www.madstop.com/ruby/ruby_has_a_distribution_problem.html
http://pkg-ruby-extras.alioth.debian.org/rubygems.html
Shoudln’t rubygems be fixed, at least in the FHS and “require_gem” respects?