BlackBerry is a line of mobile e-mail and smartphone devices developed by Canadian company Research In Motion (RIM). While including typical smartphone applications (address book, calendar, to-do lists, etc., and telephone capabilities), the BlackBerry is primarily known for its ability to send and receive Internet e-mail wherever it can access a mobile network of certain cellular phone carriers. It commands a 20.8% share of worldwide smartphone sales, making it the second most popular platform after Nokia's Symbian OS. The service is available in North America and in most European countries.
Syncronization using barry
This example syncronizes your blackberrys contacts and calender with your evolution contacts and calender. In theory the same princible should be able to be applies to other mail and calander clients. Including kmail and Google calender.
evolution - from the extra repository
msynctool-stable - from the AUR - http://aur.archlinux.org/packages.php?ID=32917
libopensync-plugin-evolution2-stable - from the AUR - http://aur.archlinux.org/packages.php?ID=39025
barry - from the AUR http://aur.archlinux.org/packages.php?ID=20874
When building barry, the PKGBUILD must be edited to enable the barry opensync plugin to be built. This must be added to the configure line in the PKGBUILD as shown below.
./configure --prefix=/usr --enable-gui --enable-opensync-plugin
Creating a sync pair
Setup evolution to use your liking if you have not done so already.
Create a sync group called evoberry
msynctool --addgroup evoberry
Add evolution and the blackberry to the sync group.
msynctool --addmember evoberry evo2-sync msynctool --addmember evoberry barry-sync
Configure the evolution member
msynctool --configure evoberry 1
Change the defaults to the location of your evolution files as shown in the example
<config> <address_path>file:///home/gary/.evolution/addressbook/local/system</address_path> <calender_path>file:///home/gary/.evolution/calendar/local/system</calender_path> <tasks_path>file:///home/gary/.evolution/tasks/local/system</tasks_path> </config>