--keyring|-k
Save or retrieve passwords from the GNOME keyring when modifying the
configuration or running a synchronization. Note that using this option
applies to *all* passwords in a configuration, so setting a single
password as follows moves the other passwords into the keyring, if
they were not stored there already:
--keyring --configure --sync-property proxyPassword=foo
When passwords were stored in the keyring, their value is set to "-"
in the configuration. This means that when running a synchronization
without the --keyring argument, the password has to be entered
interactively.
The implementation introduces new virtual methods for password handling
to properties and iterates over all properties to activate that
special behavior.
Another change is no longer to use cached strings in the SyncEvolutionConfig
to store retrieved passwords. Instead, they are saved as the filter in
the config node. This could help their users to get them but not flush
to files. The main purpose of this change is to make it flexible
to meet the requirements of dynamically added passwords in the backend.
We do depend on libsoup-2.4 after all: the API and ABI
changed considerably between 2.2->2.4.
Building D-Bus service depends on xsltproc. Added
to README and added an AC_ERROR in configure, to avoid
compile errors later on.
Compiling the GUI only works if the dbus library was built first,
so changed the default of --enable-dbus-service to "yes" if the GUI
is enabled. Added error check for conflicting configure options.
Documented dependency on GNOME keyring.
With some tweaks the autotools on Debian Etch are good enough to
compile the code. However, distributions of SyncEvolution should
better be built with recent versions of the tools and then get compiled
on Debian Etch.
We need BOOST >= 1.34 because of BOOST_FOREACH(). The configure script
now checks for this. Debian Etch can get 1.35 from www.backports.org.
That version of BOOST shows that in some files <boost/algorithm/string/join.hpp>
was not explicitly included.
These options were added already a bit earlier. The new section on
"Item Changes and Data Changes" is necessary to understand the output
about changes made during a sync.
The server config.ini files and icon.[svg|png] in src/default will be installed
in /etc/default/syncevolution. All configurations found there extend and/or
override the builtin templates. The advantage is that file-based templates
can have icons and that templates can be added/modified without recompiling
SyncEvolution.
This meta information is now part of EvolutionSyncConfig:
- getWebURL() returns a URL with further information; this
replaces the hard-coded URL string that was previously
returned as comment for templates in the ServerList
- getIconURI() currently returns absolute file paths to
an icon file (example: icon.png for ScheduleWorld). The
content and exact URI may vary, depending on how system
administrators or distributions configure SyncEvolution.
If possible, callers should be able to handle http://
and other URI access methods.
The advantages are:
- can use the default yes/no cases of CHECK_PKG_CONFIG,
which print more detailed information about which package
is missing
- slightly faster configure run without the --enable-gui and --enable-dbus-service
options
Also documented the required packages.
Configure didn't check correctly for "glib": it invoked glib-config
but didn't notice when that command was missing. Removed that
check as it has been superseeded by "glib-2.0" anyway.
Boost wasn't checked for at all, although the Boost header files are
no longer bundled.
libecal and libebook are now obligatory unless explicitly disabled.
This catches a common mistake made by users: previously syncevolution
would compile, but without Evolution support. The drawback is that
on platforms without Evolution, support for it now must be disabled
explicitly.
More explicit description of the different operations.
Added --run|-r switch: if properties are on the command
line, then an operation must be specified explicitly,
with --run standing for a sync run. Otherwise a
sync might accidentally be done when a configuration
change was intented, but the --configure switch was
forgotten.
git-svn-id: https://zeitsenke.de/svn/SyncEvolution/trunk@696 15ad00c4-1369-45f4-8270-35d70d36bdcd
- added sanity checking of properties
- added listing of properties and help for individual properties
- use user-visible string as main alias for sources
git-svn-id: https://zeitsenke.de/svn/SyncEvolution/trunk@524 15ad00c4-1369-45f4-8270-35d70d36bdcd
The API documentation of these calls doesn't say so explicitly, but it
seems that a combination of g_object_unref()/g_free()/g_list_free() is
necessary. Rewrote the eptr smart pointer so that different deleter
functions can be selected as template parameters.
git-svn-id: https://zeitsenke.de/svn/SyncEvolution/trunk@521 15ad00c4-1369-45f4-8270-35d70d36bdcd
- the new checkinstall --docdir=: syntax is used to avoid adding the name twice
- description-pak was not created and thus missing from package
git-svn-id: https://zeitsenke.de/svn/SyncEvolution/trunk@476 15ad00c4-1369-45f4-8270-35d70d36bdcd
- added dumping of local changes before sync (works best with logdir)
- added command line options:
--sync|-s <mode>
Temporarily synchronize the active sources in that mode. Useful
for a 'refresh-from-server' or 'refresh-from-client' sync which
clears all data at one end and copies all items from the other.
--status|-t
The changes made to local data since the last synchronization are
shown without starting a new one. This can be used to see in advance
whether the local data needs to be synchronized with the server.
--quiet|-q
Suppresses most of the normal output during a synchronization. The
log file still contains all the information.
--help|-h
Prints usage information.
--version
Prints the SyncEvolution version.
git-svn-id: https://zeitsenke.de/svn/SyncEvolution/trunk@449 15ad00c4-1369-45f4-8270-35d70d36bdcd
loglevel is configurable
- fixed off-by-one counting of months in backup directory names
- only one example configuration per server, users typically do not
need the _1/2 suffices and the testing system no longer has to be
configured manually either
- documented the switch from the original SyncEvolution testing to its
successor, the generic Funambol C++ client testing framework
git-svn-id: https://zeitsenke.de/svn/SyncEvolution/trunk@362 15ad00c4-1369-45f4-8270-35d70d36bdcd
