Notes for Packagers
This page contains hints and tips for people creating Audacity packages for Linux/Unix distributions. It will also be useful for people compiling audacity from source on their own systems. For more details about developing for Linux see the Developing On Linux. For almost all Mac and Windows users we would recommend using the binaries available on our website.
What to Package
Ideally, both the latest stable release of audacity and the latest beta release would be available to users, with a choice to install either or both independently. Unfortunately this (especially parallel installs) is beyond the capability of many package management systems, and so a decision will have to be made on which version to package.
Currently, the stable (1.2.6) version of audacity depends on the obsolete 2.4.x version of wxwidgets, so will be difficult to package for many systems. In practise this means that you will have to package the most recent beta release from the 1.3.x series (1.3.5 at the moment). This can be built using either the 2.6 or 2.8 versions of wxwidgets (provided that 2.6 compatibility is enabled in the wx 2.8 build). Because this is a beta release, be aware that there is limited documentation and there will be frequent new releases to address issues.
Audacity uses a lot of libraries to provide functionality. The majority of these can and should be dynamically linked as system libraries, and so listed as dependencies of the audacity package. The sources of some of these libraries are provided in the lib-src/ module of the audacity CVS, but don't regard this as evidence that they should be preferred to system copies, most are provided only as a convenience to Mac and Windows developers.
Some libraries are absolutely required for audacity to run. These are hard dependencies for any Audacity package unless the libraries are linked statically.