| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
| |
Rather than using our own _gck_debug() and _gcr_debug()
wrappers.
|
| |
|
|
|
|
|
|
|
|
|
| |
* There were problems with applications that didn't use libgck but
linked to the old version with the old libtool number: empathy
* So stub out the removed functions, revert the libtool version changes
instead of removing those functions.
This reverts commit ef7e91d66839d4104ee6ba9681e49506f5dd5fa3.
|
|
|
|
|
|
|
|
|
|
| |
* libgck API is not yet stable.
* Gck is only used internally in the gcr projcet, gnome-keyring project
and the seahorse project.
* We want to be threadsafe with regard to attributes, and the
functions removed can't be implemented within the new framework.
* Remove deprecated functions at the same time, since this is an
opportunity to cleanup.
|
|
|
|
|
|
|
| |
* And allow updating of the attributes, in particula adding
attributes that are discovered.
* Add a gck_object_cache_lookup() methods which load attributes
and then updates the cache if the object has a cache.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=664832
|
|
* And detect the mechanisms supported on a given key.
|