[horde] Horde 4.0.2 exhauses memory

[Patrick Boutilier]

On 05/03/2011 12:22 PM, Patrick Domack wrote:
>
> Quoting Reindl Harald <h.reindl at thelounge.net>:
>
>> And that is why i hate pear and want to use my rmps built from
>> tarballs as all
>> the years before and SURE nobody needs to make this tarballs by hand,
>> this
>> could be done automatic on the horde-servers and instead hundrets auf
>> small
>> packages in the same structure as below
>>
>> -rw-r----- 1 builduser builduser 3,3K 2010-10-31 11:12 horde-dimp.spec
>> -rw-r----- 1 builduser builduser 7,4K 2010-10-31 11:12 horde-imp.spec
>> -rw-r----- 1 builduser builduser 5,5K 2010-09-29 14:46 horde-ingo.spec
>> -rw-r----- 1 builduser builduser 4,1K 2010-09-29 14:46
>> horde-kronolith.spec
>> -rw-r----- 1 builduser builduser 3,2K 2010-09-07 23:41 horde-mimp.spec
>> -rw-r----- 1 builduser builduser 3,3K 2010-09-29 14:45 horde-nag.spec
>> -rw-r----- 1 builduser builduser 16K 2010-11-27 13:37 horde.spec
>> -rw-r----- 1 builduser builduser 6,4K 2010-09-29 14:46 horde-turba.spec
>> -rw-r----- 1 builduser builduser 3,3K 2010-09-07 23:41 horde-whups.spec
>>
>> WHAT SPEAKS AGAINST PEAR:
>> * rpm does not mix config/app-files
>> * rpm will install clean .rpmnew-files while update
>> * rpm can be tested on one machine and deplyoed in a defined version
>> * rpm have clean way for downgrades
>> * PEAR is packing all in one folder
>> * PEAR-Packages including configs can not be deployed
>> * PEAR-Packages have no defined version over a defined timeline
>>
>
> Well, bugs are bugs.
>
> But the overwriting of the config files is extreemly annoying.
>
> On each update, it wipes out my imp backend and mime_drivers configs.
>
>

I believe you should copy the default files to backends.local.php and 
mime_drivers.local.php and then make changes to the new files.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: boutilpj.vcf
Type: text/x-vcard
Size: 286 bytes
Desc: not available
URL: <http://lists.horde.org/archives/horde/attachments/20110503/f64d305a/attachment.vcf>