CouchDB Packaging Discussion

packaging.md

CouchDB Packaging

People present:

• Andy W.
• Jan L.
• Noah S.
• Robert K.
• Robert N.
• Klaus T.
• bunch of others

objectives

• do a new release (doesn't have to be 2.0)
• have all channels available
• packaging model: CouchDB first, NOT distribution first
• maintainable
• documented

challenges

• distribution (aka Debian) vs. CouchDB
• Debian as an example
• Cloudant specific shape of the artifact
  • depending on the outcome of this Cloudant may or may not adopt it
  • hot updates = production ready
  • if multiple versions are possible or bundled
  • then adoption is very likely

differences to Debian

• all dependencies are bundled
• need to be able to run different versions of Erlang
• old and new dependencies need to be installed at the same time
• examples: Java, Python, PHP
• special issue: OpenSSL

dependencies

• examples
  • spidermonkey
  • mochiweb
  • erlang
  • fabric
  • ...
• package names need to have versions included

current blocker: tarball release

• make dist, clean need work/are missing
• result "doesn't require a network connection" — Robert N.

outcomes

1. do a tarball release
2. (result from tarball) Apache CouchDB hot-upgradable .deb, .rpm, homebrew, ... for 2.0 (CouchDB first)
3. (result from 2) start dialog with distributions about splitting packages by version