Create a package definition for Debian/Linux systems.
- at least for an OpenCine interface library
- possibly for OpenCine as a whole (likely to be simpler to do it this way)
In the Linux world, offering a well maintained package makes your application a first class citizen. While there are several packaging systems, the Debian framework has the reputation of a well organised and somewhat demanding quality standard. Thus, if your package makes it through Debian's "linitian check" (automated compliance check), you've probably addressed all the relevant issues and have a solid foundation for other distributions as well. If you have a working DEB, then usually it's just a minor itch to create a RPM spec file (to cover the RedHat-Familiy of distributrions). Moreover, a lot of popular distributions immediately consume, recompile and distribute Debian packages (Ubuntu, Linux Mint,....)
OpenCine uses a portable CMake build system and Debian offers a mature set of scripts and best practices for such. So this task boils down to
- verify the usual points which could be problematic (licenses, release cycle considerations, special dependencies not available in standard distros)
- find the existing package names and versions for all required debendencies
- set up the packaging scripts. My (@Ichthyo) recommendation is to rely on
* CDBS
* git-buildpackage
After this is done, you'll be able to deliver new Linux packages for a release with just some git and script invocations (which, after some rehearsal, can be fully automated)