= QuteCom Packaging =

== what is a software package ? ==

A software package is a group of components that together create the software. These components naturally include the executables that comprise the software, but they may also include meta-information files and can also include other information files and scripts.

Under GNU/Linux, you can find several types of packages standard (.deb, .rpm, ...). Under Windows and MacOSX, other best practices exist for packaging.

The Art of packaging takes a lot of knowledge of the target system, mostly because dependency management is a hard thing to achieve.

== How is QuteCom packaged ? ==

=== under GNU/Linux ===

Under GNU/Linux, a lot of effort is being made by the QuteCom community to find the best solution to a very hard problem:
 * discover and adapt to the default installed libraries on a given distribution
 * innovate while avoiding the most recent versions of software that is not packaged by QuteCom
 * debug or modify some behavior of external libraries and then try to submit patches upstream in the original project (and try to get the commited)

A specific page will be dedicated to hold information about [wiki:QuteComPackagingLinux packaging under Linux]

=== under Windows ===

A specific page will be dedicated to hold information about [wiki:QuteComPackagingWindows packaging under windows]

=== under MacOSX ===

A specific page will be dedicated to hold information about [wiki:QuteComPackagingMacOSX packaging under MacOSX]

== The common grounds ==

Some aspects of packaging are common to all platforms or at least must be faced under each platform. They are listed here

* [wiki:QuteComPackagingPlugins | default plugin directories]

== references ==
 
 * source tarball helper scripts :
   * http://svn.debian.org/wsvn/pkg-voip/wengophone/trunk/debian/get-orig-source.sh?op=file&rev=0&sc=0
   * http://svn.debian.org/wsvn/pkg-voip/wengophone/branches/cmake/debian/get-orig-source.sh?op=file&rev=0&sc=0