asterisk: cyclic-deps, gtk, docs

[Tzafrir Cohen]

On Thu, Aug 17, 2006 at 11:59:17PM +0200, Jonas Smedegaard wrote:
> On Thu, 17 Aug 2006 21:42:33 +0100 Mark Purcell wrote:
> 
> > Init.d will fail if the asterisk daemon isn't present.
> > 
> > But the default install doesn't start asterisk on load, 

Which is something I want to change anyway.

> > until
> > default/asterisk is modified anyway..

One way out of it is not to put /etc/default/asterisk in the package.
The way it is now, every upgrade of asterisk updates that file. That
file can have nothing by default. 

> 
> Not good enough: removing (but not purging) an earlier asterisk leaves
> a (possibly enabled!) default/asterisk that then may cause trouble on
> install, as you cannot be sure of the order of install of packages.
> 
> Package asterisk can then instead predepend on one of the packages
> containing the binary, but predepends should generally be avoided.
> 
> 

If the package that contains /usr/sbin/asterisk is not at least unpacked
when the package that contains /etc/init.d/asterisk is configured,
asterisk will fail to start.

> > > 3. The build requirement for asterisk was removed. However how do we
> > > guarantee that the gtk module is not built accidentally?
> > > BuildConfilict on the gtk lib, or an explicit rm of the generated
> > > module?
> > 
> > I don't think it is an issue, if it gets built accidentally.
> > Certainly the buildd's shouldn't so the archive should be ok, it is
> > rather someones home brewed asterisk that might have that problem.
> > But then it shouldn't be critical for them either.

an explicit 'rm' (as was used in earlier versions, when there was a
separate package) will also do.

Not a blocker. I'll update the rules file.

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