asterisk-config upgrades

Paul Cupis paul@cupis.co.uk
Sun, 08 May 2005 10:55:34 +0100


At Thu, 28 Apr 2005 21:51:09 +0200, Kilian Krause <kk@verfaction.de> wrote:
> Tzafrir wrote:
>> asterisk currently depends on asterisk-config of exactly the same
>> version. This means that every upgrade of the package asterisk forces an
>> upgrade of the package asterisk-config.
> 
> yep.
> 
>> Furthermore, many people don't want the defualt config files. They want
>> their own custom set. Such a dependency does not allow me to create a
>> dummy/partial config package so that asterisk-config will not be
>> installed.
> 
>> Why is the dependency on the exact version? What is the actual minimal
>> version required? Alternatively, make it depende on:
>>
>>   asterisk-config=exact-version || asterisk-config-custum
>>
> 
> well, it's 2 reasons:
> 1.) Debian doesn't allow to Depends on packages not in the archive. That
> above alternative would be a broken reference and thus
> policy-nonconformant

This is not true. You can have a conditional dependancy which can be
filled with a package not in Debian. Please see the exim4 package for an
example.

Package: exim4
Priority: important
Version: 4.50-6
Depends: exim4-base (>= 4.50), exim4-daemon-light | exim4-daemon-heavy |
exim4-daemon-custom

$ apt-cache show exim4-daemon-custom
$

Personally, I think that adding this conditional dependancy on an
admin/local config package would be a good thing.

Regards,

Paul Cupis
-- 
paul@cupis.co.uk