summaryrefslogtreecommitdiff
path: root/gio/giomodule.c
diff options
context:
space:
mode:
authorMatthias Clasen <mclasen@redhat.com>2010-04-18 15:55:14 -0400
committerMatthias Clasen <mclasen@redhat.com>2010-04-18 15:55:14 -0400
commitfd8cdb83e1b5a4b71aa84ca26a000e2fbd7a3d37 (patch)
treeec3f9510f07b9b8eb9bd12fc84ee53ad6559ef9b /gio/giomodule.c
parentb7afff0033a43c10012491ab44d2abd4b06bd039 (diff)
downloadglib-fd8cdb83e1b5a4b71aa84ca26a000e2fbd7a3d37.tar.gz
glib-fd8cdb83e1b5a4b71aa84ca26a000e2fbd7a3d37.tar.bz2
glib-fd8cdb83e1b5a4b71aa84ca26a000e2fbd7a3d37.zip
Refer to gio-querymodules in the extension point docs
Diffstat (limited to 'gio/giomodule.c')
-rw-r--r--gio/giomodule.c8
1 files changed, 7 insertions, 1 deletions
diff --git a/gio/giomodule.c b/gio/giomodule.c
index 587cc81c7..e1b1d1748 100644
--- a/gio/giomodule.c
+++ b/gio/giomodule.c
@@ -90,7 +90,13 @@
* it uses the implementations that have been associated with it.
* Depending on the use case, it may use all implementations, or
* only the one with the highest priority, or pick a specific
- * one by name.
+ * one by name.
+ *
+ * To avoid opening all modules just to find out what extension
+ * points they implement, GIO makes use of a caching mechanism,
+ * see <link linkend="gio-querymodules">gio-querymodules</link>.
+ * You are expected to run this command after installing a
+ * GIO module.
*/
struct _GIOModule {
GTypeModule parent_instance;