Kolab Server 2.2.1 Beta 1

[Albrecht Dreß]

Hi Gunnar:

Am 14.12.08 16:53 schrieb(en) Gunnar Wrobel:
> It should actually not be too hard to write a tool if you use the  
> standard "Prefs" module from Horde  
> (http://cvs.horde.org/framework/Prefs/). You will need to initiate it  
> once with the standard "kolab" driver backend, read and serialize the  
> prefernces of each user and pipe them back into the preferences  
> system, this time using the "file" driver.

Thanks for that hint - I have *no* experience with php, but a few extra  
days of vacation over xmas, so I should be able to have something at  
the beginning of January at the latest, so stay tuned.  Is it ok to  
open an issue for that once I have something?

> As I mentioned in that issue I cannot use the patch as you provided  
> it at the moment. It is a good idea in general but for structural  
> reasons such a functionality belongs into the Kolab_Server package.  
> Specifically into  
> http://cvs.horde.org/framework/Kolab_Server/lib/Horde/Kolab/Session.php.
> 
> Your initHorde() function should be added in the initial session  
> setup (function Horde_Kolab_Session()). And it needs to use the  
> standard preferences setup in order to inject the configurations into  
> the preferences system. You hardcoded the injection into LDAP. If you  
> place it into the Session manager and just use the general  
> Preferences interface you will be able to initiate the Preference  
> whatever backend driver is being used ("ldap", "file", or  
> "kolab_imap").
> 
> I'm writing this so that if you invest the effort in updating it it  
> could be really added directly.

Yes, I will do that - my approach was somewhat naive, and the only  
thing I can mention in favour of it is that it works nicely in /my/  
2.2.0 environment...  But of course you're right that it should go into  
the standard prefs system.  I actually hacked a lot more meanwhile  
which is specific for my company.  Maybe a template-like init file  
would be nice, at least for small organisations like ours (not suitable  
for bigger ones like the BSI, though!).  Again, don't expect anything  
too fast, but I'll definitively will work on that!

Oh, and, btw, I will of course also update my samba patches (#2997 &  
the Wiki page), which I need in my setup...

> Both should be fixed in the newer release.

Cool, thanks, I just was a little worried that it got lost... ;-)

Again, I am *really* curious about the new release, and it's great to  
have it quickly after 2.2.0, in particular as I had *much* trouble with  
it.  Now the main thing which I'm concerned about is #2982, which is  
clearly an OpenLDAP (or Berkely DB, or 64-bit?) related one; maybe the  
upgrade is an improvement...

Cheers, Albrecht.