Packaging for LINUX

Branching policy

• master: contains cutting-edge stable development code for the next major or minor release.
• releases/X.X: contains patches as well as the latest releases (tags) of the X.X release line.

For package maintainers we recommend the following scheme:

• stable packages: should always be based on tagged releases.
• development packages: should target the latest releases/X.X branch until a beta version of the next major/minor release is tagged on master.

---

! WARNING : this part may be out of date !

---

If you are a package maintainer and wish for your packaging scripts to be included in the Hydrogen source tree, we would be happy to work with you. Please contact the developer mailing list (see the Hydrogen home page). The instructions below are for the package systems that have been contributed so far.

Creating a .deb Package

In order to create a .deb package for Debian-based systems (like Debian, Devuan, Ubuntu, or Mint), you first need the debhelper package:

$ sudo apt-get install debhelper

To build the Hydrogen package, run the following commands.

$ git clone git://github.com/hydrogen-music/hydrogen.git
$ cd hydrogen
$ cd linux
$ dpkg-buildpackage -rfakeroot -b -uc -us

This will place the .deb package and description files in the parent directory. If you wish to change the version number for the archive, edit linux/debian/changelog to set the version. To install the newly created deb package, run the following (substitute the deb package name with the version your build created):

$ cd ..
$ sudo dpkg -i hydrogen_X.Y.Z_amd64.deb