| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
With glib requirements now being 2.38, these functions do not make sense anymore.
Signed-off-by: Eduardo Lima (Etrunko) <etrunko@redhat.com>
|
|
|
|
|
|
|
|
|
|
| |
Since 2.31, g_mutex_new() is deprecated.
Based on commit 2dc7476d32a9e158e688486e8f184c719c53bb4c from
libvirt-glib.
Original author: Daniel P. Berrange <berrange@redhat.com>
Related to: rhbz#1243228
|
|
|
|
|
| |
There is no need to have more than one glib version checking for the
same version, in the same file. Let's just group them all.
|
|
|
|
|
| |
G_SOURCE_REMOVE was introduced in GLib 2.32 and has its value defined as
FALSE.
|
|
|
|
|
|
| |
Recent commits introduced use of g_clear_object and
g_byte_array_new_take which are only present respectively in glib
2.28 and 2.32
|
|
We use API from 2.22, and some from further version. Add
virt-glib-compat.h fallback file for those.
|