* It's clearer what happens here: we try to remove as many matching
passwords as possible.
* Also rename secret_service_remove() to secret_service_clear()
* Rename secret_password_clear() which used to wipe password memory
to secret_password_wipe().
Don't set PKG_CONFIG_PATH, this breaks jhbuild; instead, use
--include-uninstalled to tell the scanner where to find internal
libraries.
Don't set _PACKAGES = gio-2.0; we already pick that up from the
Gio-2.0.gir.
https://bugzilla.gnome.org/show_bug.cgi?id=679852
* We want to settle on 1 after first stable release
* Since we're going to start patching projects we want this to have
the pkg-config file be libsecret-1
* C callers need to use libsecret-0 pkg-config file for stable and
libsecret-unstable for unstable stuff.
* Vala callers need to '--pkg libsecret-unstable' for unstable
* GObject Introspection callers need to use the SecretUnstable package
* Death by a thousand paper cuts from gir and vapi not liking
the fact that the secret.h file was not usable uninstalled
and installed in the same way.
* When matching items, make sure we have attributes if
no schema name was included in the match
* This is particularly important because we don't want to
remove all the items.
* libsecret-@SECRET_MAJOR@.vapi is built only with those 2 defines and these
were not checked before depending that target for the test case
Found during jhbuild run
* Make SECRET_COLLECTION_DEFAULT and SECRET_COLLECTION_SESSION
be the simple aliases for those collections.
* Accept either an alias or a path in secret_password_store()
and secret_service_store() and friends.
* They all contain '_dbus_path' in their name
* Move secret_service_get_session_path() to the paths functionality
* Move the secret_collection_new() and secret_item_new() functionality
to the path based section.
* In tests make sure notifications settle down before waiting
on new notifications. This fixes random test crashes.
* Using async here means all signals are delivered by the time
we get the new object.
* We use secret_service_get() to lookup the default
SecretService in these cases.
* Use this functionality in the secret_password_xxx()
functions to greatly simplify them.
* And flags to prevent loading of items when creating a
SecretCollection object
* Rename secret_service_ensure_collections() to
secret_service_load_collections()
* Turn secret_service_search() and friends into a more convenient
API, so that callers can get attributes, unlocking, and secrets
if so desired.
* Also support retrieving either one secret, or all of them.
* Make sure this property is kept in sync so it can be used
immediately in the logic to retrieve secrets or other stuff.
* We don't wait for a PropertiesChanged, which may come later
