Permalink
Browse files

[docs] clarify README

  • Loading branch information...
1 parent ff7203b commit ed0f728954536c37cef20934c9ed0f603f960b77 @dieterv committed Nov 16, 2010
Showing with 5 additions and 5 deletions.
  1. +4 −4 README.rst
  2. +1 −1 bin/build_bindings.sh
8 README.rst
@@ -5,10 +5,10 @@ pygtk-installer
The pygtk-installer project provides:
- build_bindings.sh: a tool that builds windows installer packages (both .exe
- and .msi) for pygtk and dependencies.
+ and .msi) for pycairo, pygobject, pygtk, pygoocanvas, pygtksourceview and pyrsvg.
- build_installer.py: a tool that generates an all-in-one installer bundling
the separate .msi installers created by build_bindings.sh and the gtk+ runtime
- from ftp.gnome.org/pub/GNOME/binaries/win32/.
+ packages from ftp.gnome.org/pub/GNOME/binaries/win32/.
=======
WARNING
@@ -26,10 +26,10 @@ If you decide to give it a test anyway:
The pygtk version that's installed with the all-in-one installer
should take care of loading the included gtk+ runtime on PATH
when you import pygtk; pygtk.require('2.0'). As a consequence
- simply importing gtk, gobject, etc might not work without
+ simply importing gtk, gobject, etc *might* not work without
the .require() call. The .require() call is typically done only
once in a startup script somewhere.
-#. Why did you say "might not work" above? Ah, good question. If
+#. Why did you say "*might* not work" above? Ah, good question. If
you've got another gtk+ runtime on your PATH environment variable - for
example you installed Dia, MonoDevelop (gtk#), etc. - the PyGTK bindings might
use one of those runtime libraries. In that case the behavior of the PyGTK
View
2 bin/build_bindings.sh
@@ -1,6 +1,6 @@
#!/bin/bash
-# Copyright © 2010 pygtk-installer Contributors
+# Copyright © 2010 pygtk-installer Contributors
#
# This file is part of pygtk-installer.
#

0 comments on commit ed0f728

Please sign in to comment.