FreePBX 2.3 packaging - need some help

[Tzafrir Cohen]

On Sun, Jul 22, 2007 at 02:58:32PM +0300, Diego Iastrubni wrote:
> Hi all,
> 
> I need help with freepbx 2.3, as the folks upstream are doing something very 
> weird. 
> 
> The source freepbx is spited in build time to asterisk-config-asterisk, 
> freepbx-common, and other goodies. For version 2.3, I need to split 
> freepbx-common to freepbx-common and freepbx-module-core.
> 
> The reason for this that the core module, will be updated also from the 
> updates repositories. In reality it means that freepbx-module-core-2.3.0 will 
> come from the source package "freepbx" and freepbx-module-core-2.3.1 will 
> come as an update, and will be built from source 
> freepbx-module-core-2.3.1.tgz. From the user point of view, it does not 
> matter since apt will install the package anyway. However, I am not sure if 
> the number of Debian policies broken here is a 2 digit number.

So we will have an older copy of the core module coming throuh the
tarballs, and newer ones coming through the modules distribution
mechanism.

> 
> I see 2 options:
> 1) Continue as before, since apt-get will not care about this situation.
> 2) Remove the module packages from the repositories, and let the GUI handle 
> those updates, lime "upstream" does. This means that the freepbx package must 
> be writable at run time by the web browser.

3) Ignore the core module in the freepbx tarball, and package it just
like any other module we package.

But wait, we don't package modules as packages, right? Looks like we'll
havve to start.

Either we package all the modules as a single package, or we package
each module in a package of its own.

-- 
               Tzafrir Cohen       
icq#16849755                    jabber:tzafrir at jabber.org
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com       
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir