[glib] Skip g_subprocess_launcher_set_child_setup() in introspection

[Philip Withnall <pwithnall src gnome org>]

commit e5db8ec787ca4c09d38c638c4529de45d89ec236
Author: Mikhail Zabaluev <mikhail zabaluev gmail com>
Date:   Sun Oct 5 21:04:00 2014 +0300

    Skip g_subprocess_launcher_set_child_setup() in introspection
    
    It's not likely that the runtime of a bound language using the
    introspection supports running in a process forked by a foreign
    library, so that a closure programmed in that language would work
    safely.
    
    Any programming environment supporting that would probably have
    its own advanced facilities for process spawning, or be able
    to access the GLib spawning APIs via raw C bindings (still
    represented in the introspection, (skip) only adds a flag)
    and do any low-level preparatory dances as necessary for the
    forked runtime.
    
    Note that there are other APIs making use of GSpawnChildSetupFunc,
    but they are usable with the closure nullified, and we cannot annotate
    the closure parameters away because that would break the annotated API
    for bindings; accordingly to bug #738176 comment #3, the current bindings'
    users are expected to pass null.

 gio/gsubprocesslauncher.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/gio/gsubprocesslauncher.c b/gio/gsubprocesslauncher.c
index 4c9758b..875fdb5 100644
--- a/gio/gsubprocesslauncher.c
+++ b/gio/gsubprocesslauncher.c
@@ -640,7 +640,7 @@ g_subprocess_launcher_take_fd (GSubprocessLauncher   *self,
 }
 
 /**
- * g_subprocess_launcher_set_child_setup:
+ * g_subprocess_launcher_set_child_setup: (skip)
  * @self: a #GSubprocessLauncher
  * @child_setup: a #GSpawnChildSetupFunc to use as the child setup function
  * @user_data: user data for @child_setup