[sync] best policy for versions and maintenance

[Jan Schneider]

Zitat von Jamie McClelland <jm at mayfirst.org>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all,
>
> I've given up on the black berry client and started putting my  
> effort into the
> funambol outlook client which seems better supported (so our black  
> berry users
> will have to sync to outlook, and then sync outlook to horde).
>
> In my latest test with funambol outlook and horde (cvs head) it all seems to
> work out great. Yay!
>
> Now, I'm trying to figure out how to back pedal from using the most  
> recent cvs
> version of horde in a production environment.
>
> Using the packages from debian stable (horde 3.1.3) and the most recent
> published stable from the horde web site (horde 3.1.5) fails. Not sure
> debugging the failure is worth the trouble since the SyncML packages have
> undergone a lot of development since these versions were released.
>
> So - I tried backing up the SyncML packages from these two distributions and
> putting in the most recent SyncML package in their place (CVS versions from
> today). In both cases (3.1.5 and 3.1.3) I get this error:
>
> <b>Fatal error</b>:  Class 'SyncML_SyncmlHdr' not found in
> <b>/usr/local/share/horde-stable-upstream/horde/lib/Horde/RPC/syncml.php</b>
> on line <b>202</b><br />
>
> Seems like in previous versions a different class name was used.
>
> Does anyone have suggestions for how to use the most recent SyncML packages
> without having to use bleeding edge Horde code? Is there any easy patch to
> backport SyncML to work with these older versions of Horde? Or - am I doing
> something wrong?

No, there is no easy way, and I wouldn't even try to backport it.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/