summaryrefslogtreecommitdiff
path: root/README.in
diff options
context:
space:
mode:
authorMatthias Clasen <mclasen@redhat.com>2009-10-01 11:41:17 -0400
committerMatthias Clasen <mclasen@redhat.com>2009-10-01 11:45:28 -0400
commit97d15954ad426ea792e1c237dfefe754614a0e9e (patch)
tree44771107b4124aca9115bd60b403d820463b3ebf /README.in
parent42ad005847e9270d39ef692291fc95dfb96750fb (diff)
downloadgdk-pixbuf-97d15954ad426ea792e1c237dfefe754614a0e9e.tar.gz
Move SIGPIPE suppression to gtk_init and document it
Some people were unhappy with doing it deep inside the lpr print backend at an unpredictable time, and SIGPIPE is almost never wanted anyway.
Diffstat (limited to 'README.in')
-rw-r--r--README.in5
1 files changed, 5 insertions, 0 deletions
diff --git a/README.in b/README.in
index bc2f857aa..84d6329e0 100644
--- a/README.in
+++ b/README.in
@@ -44,6 +44,11 @@ Release notes for 2.18
GDK_NATIVE_WINDOWS makes GDK create a native X11 window for each
GDK window, which might make problematic applications work better.
+* GTK+ calls signal (SIGPIPE, SIG_IGN) during initialization, to ignore
+ SIGPIPE signals, since these are almost never wanted in graphical
+ applications. If you do need to handle SIGPIPE for some reason, reset
+ the handler after gtk_init(), but notice that other libraries (e.g.
+ libdbus or gvfs) might do similar things.
Release notes for 2.16
======================