summaryrefslogtreecommitdiff
path: root/data
diff options
context:
space:
mode:
authorThomas Haller <thaller@redhat.com>2017-03-17 11:01:38 +0100
committerThomas Haller <thaller@redhat.com>2017-03-17 13:00:32 +0100
commit5022e3b8eea47bbbebf2cf557b24413b6fa6de52 (patch)
tree3c620e72b3f8168a0e90f93b97b88c56d0182aba /data
parente65aa9e6ffee48e3f98f0a0dc6b3aec7e6dc872c (diff)
downloadNetworkManager-5022e3b8eea47bbbebf2cf557b24413b6fa6de52.tar.gz
libnm: revert coercing NMVpnConnectionStateReason to NMActiveConnectionStateReason
NMVpnConnectionStateReason is no longer used and replaced by NMActiveConnectionStateReason. However, the old enums should stay in place as they were: Otherwise: #define NMVpnConnectionStateReason NMActiveConnectionStateReason causes compiler warnings: NMVpnConnectionStateReason x; x = NM_VPN_CONNECTION_STATE_REASON_UNKNOWN; // -Wenum-conversion if (x == NM_VPN_CONNECTION_STATE_REASON_NO_SECRETS) { } // -Wenum-compare Similarly, a user who didn't upgrade shall continue to get the old GType for NM_TYPE_VPN_CONNECTION_STATE_REASON. In practice, old users will have no issues using the old enum the places where it worked before. The only use of the deprecated enum is in vpn_state_changed() signal slot of NMVpnConnection. This makes the signal slot itself deprecated. However, NMVpnConnection is an NMObject and commonly created within libnm itself, not by the user. It is very unlikely that a user of libnm subclassed NMVpnConnection and makes use of the vpn_state_changed() signal slot. So, deprecate it without replacement. Fixes: a91369f80d44d1fc748fc3a9f5d9ef0fb566c77c
Diffstat (limited to 'data')
0 files changed, 0 insertions, 0 deletions