[php-maint] libkolab* in Debian

[Ondřej Surý]

The reason for ucf is to avoid the "config file has been changed what
do you want to do", when no upstream change has happened.

E.g. when I comment out the extension= line, I don't get bothered
every time I install new package.

So it's just a matter of taste how much do you want to annoy your users :)

O.

On Tue, May 14, 2013 at 10:48 PM, Paul Klos <kolab at klos2day.nl> wrote:
> Op maandag 13 mei 2013 23:45:08 schreef Ondřej Surý:
>> I have checked the debian/php-*, debian/control and debian/rules and
>> they look sane to me.
>>
>> O.
>>
> Thanks, that's great to hear!
>
> I do have a question myself, though. Actually I kind of 'inherited' this package and there's one thing going on that I don't quite understand. It installs an ini file to declare the extension into /usr/share/php5/kolab. It then uses dpkg-maintscript-helper and ucf to place the ini file into /etc/php/mods-available, and finally php5{en|dis}mod to enable/disable the module.
>
> I've looked at other packages that install PHP modules. Some of those use similar methods, but others just install their ini file into /etc/php/mods-available and enable the module.
>
> Is there any kind of guidance as to when which method should be used?
>
> Cheers,
>
> Paul
>
>
> PGP: 8FE6E0BD
> _______________________________________________
> pkg-php-maint mailing list
> pkg-php-maint at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint



-- 
Ondřej Surý <ondrej at sury.org>