On Wed, 2013-05-15 at 02:03 +0530, Victor Jonathon Calel wrote:
Thanks Patrick, for sharing this information beforehand.
I work for Credence-Group & we have two different servers. We use
SyncEvolution for for syncing evolution-data. Our backup server still
runs on Ubuntu 10.04 & lots of other desktop-computer (for
clients/employees) runs on Ubuntu 10.10/11.04. We are trying to
migrate to Ubuntu 12.04 but it will take some time.
Thanks for the information. Ubuntu 10.04 for desktops will reach its end
of life (= no more security updates) this month. 10.04 for servers will
be supported longer, but I guess I'll make the jump to a newer baseline
for SyncEvolution 1.4.
I'll make sure that the source still compiles on older distros. That's
necessary for the Nokia Internet Tablets and the N9.
We are currently using syncevolution-1.3-2 (syncevolution-bundle)
& it
works perfectly (kudos to entire syncevolution-team for that!). And We
intend to stay at 1.3-2 for the time being.
I'm sure it'll take a few more months before 1.4 is ready. I don't have
a firm timeline yet, though.
I noticed older binaries are available at
http://downloads.syncevolution.org/syncevolution/archive/ but found it
as meta packages.
I got confused between two other archives: syncevolution-bundle
(
http://downloads.syncevolution.org/syncevolution/bundle/) &
syncevolution-evolution
(
http://downloads.syncevolution.org/syncevolution/evolution/) . What
is the difference between these two?
The syncevolution-bundle can be installed without also having to install
Evolution libs or KDE. The backends for these PIM storages will just not
be usable without them. syncevolution-evolution and syncevolution-kde
are meta packages with additional dependencies on the Evolution resp.
KDE/Akonadi libraries, so when installing those, one can be sure to have
a usable system.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.