delta/NetworkManager.git/include, branch th/printf

core: add compatibility wrapper for g_test_add_data_func_full() to nm-glib-compat.h

2014-08-22T13:24:31+00:00

Signed-off-by: Thomas Haller

nmtst: add assertion functions for verify() connection

2014-08-22T13:24:30+00:00

Signed-off-by: Thomas Haller

nmtst: add nmtst_assert_connection_equals() function

2014-08-22T13:24:30+00:00

Signed-off-by: Thomas Haller

nmtst: add nmtst_connection_normalize() function

2014-08-22T13:24:30+00:00

Signed-off-by: Thomas Haller

libnm-core, libnm, core: make NMConnection an interface

2014-08-16T14:17:53+00:00

The fact that NMRemoteConnection has to be an NMConnection and
therefore can't be an NMObject means that it needs to reimplement bits
of NMObject functionality (and likewise NMObject needs some special
magic to deal with it). Likewise, we will need a daemon-side
equivalent of NMObject as part of the gdbus port, and we would want
NMSettingsConnection to be able to inherit from this as well.

Solve this problem by making NMConnection into an interface, and
having NMRemoteConnection and NMSettingsConnection implement it. (We
use some hacks to keep the GHashTable of NMSettings objects inside
nm-connection.c rather than having to be implemented by the
implementations.)

Since NMConnection is no longer an instantiable type, this adds
NMSimpleConnection to replace the various non-D-Bus-based uses of
NMConnection throughout the code. nm_connection_new() becomes
nm_simple_connection_new(), nm_connection_new_from_hash() becomes
nm_simple_connection_new_from_hash(), and nm_connection_duplicate()
becomes nm_simple_connection_new_clone().

libnm-core: move some fake NMConnection methods over to NMSetting

2014-08-16T14:17:53+00:00

nm_connection_lookup_setting_type() and
nm_connection_lookup_setting_type_by_quark() have nothing to do with
NMConnection. So move them to NMSetting (and rename them to
nm_setting_lookup_type() and nm_setting_lookup_type_by_quark()).

all: fix up multiple-include-guard defines

2014-08-16T14:17:14+00:00

Previously, src/nm-ip4-config.h, libnm/nm-ip4-config.h, and
libnm-glib/nm-ip4-config.h all used "NM_IP4_CONFIG_H" as an include
guard, which meant that nm-test-utils.h could not tell which of them
was being included (and so, eg, if you tried to include
nm-ip4-config.h in a libnm test, it would fail to compile because
nm-test-utils.h was referring to symbols in src/nm-ip4-config.h).

Fix this by changing the include guards in the non-API-stable parts of
the tree:

  - libnm-glib/nm-ip4-config.h remains   NM_IP4_CONFIG_H
  - libnm/nm-ip4-config.h now uses     __NM_IP4_CONFIG_H__
  - src/nm-ip4-config.h now uses       __NETWORKMANAGER_IP4_CONFIG_H__

And likewise for all other headers.

The two non-"nm"-prefixed headers, libnm/NetworkManager.h and
src/NetworkManagerUtils.h are now __NETWORKMANAGER_H__ and
__NETWORKMANAGER_UTILS_H__ respectively, which, while not entirely
consistent with the general scheme, do still mostly make sense in
isolation.

nmtst: fix memory leak in nmtst_create_minimal_connection()

2014-08-07T20:26:28+00:00

Signed-off-by: Thomas Haller

nmtst: add nmtst_create_minimal_connection() function

2014-08-07T19:43:43+00:00

Signed-off-by: Thomas Haller

include: drop nm-settings-flags.h, move NMSecretAgentGetSecretsFlags

2014-08-01T18:34:39+00:00

For some reason, the flags used by o.fd.NM.SecretAgent.GetSecrets were
defined as both NMSecretAgentGetSecretsFlags in
libnm{,-glib}/nm-secret-agent.h, and then separately as
NMSettingsGetSecretsFlags in include/nm-settings-flags.h.
(NMSettingsGetSecretsFlags also had an additional internal-use-only
value, but that was added later after the duplication already
existed.)

Fix this by moving NMSecretAgentGetSecretsFlags from libnm to
nm-dbus-interface.h, adding the internal-use-only value to it as well,
updating the core code to use that, and then removing
nm-settings-flags.h.