asterisk: cyclic-deps, gtk, docs

[Tzafrir Cohen]

On Sat, Aug 19, 2006 at 06:32:48PM +0200, Jonas Smedegaard wrote:
> On Sat, 19 Aug 2006 18:20:36 +0300 Tzafrir Cohen wrote:
> 
> > 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.
> 
> Great!
> 
> 
> > > > 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. 
> 
> That file is (and must be) a conffile. As such, you are incorrect:
> 
> The file is only updated if accepted by the local admin. And requests
> for updates are only done each time the content of the packaged file
> changes between installed and to-be-installed package.

This is nice in theory.

In practice any upgrade of asterisk would be accompanied by an upgrade
of asterisk-config, which updates tons of config files. Thus you'll get
asked many times if you want to accept or reject changes. This is a
pain. Most users will take the "safe" way of not updating, and then the
update of asterisk-config would be just a waste.

> 
> 
> If we want to change the default of the package from not starting the
> daemon to starting it, then the correct approach is to simply change
> the packaged file.
> 
> That way users updating the package are made aware of the change.
> 
> That's the point of conffiles - don't try to defeat that :-)

I just say that a sane default is an empty file. No point in creating
extra work for the userwhere none is needed in the first place.

> 
> 
> > > 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.
> 
> Correct. That's another uglines of this.
> 
> The maintainer of dovecot solved similar issues among the binary
> packages dovecot-imapd, dovecot-pop3d and dovecot-common.
> 
>  * dovecot-common provides sysV script
> 
>  * SysV "start" action fails silently if binary does not exist
> 
>  * SysV "start" action uses treats already running as no error
> 
> 
> That last one bit me today: Some package other than asterisk itself is
> updated in same batch as asterisk, restarts the daemon, and when
> asterisk later attempts to start it again after updating, it fails,
> telling to use restart instead.

Could you please be more specific? I don't follow you here.

-- 
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