Indicate that Python is required to compile Wireshark.

Remove some trailing white space at the same time.

(The ./configure options in INSTALL are significantly out of date--that will
be the subject of a separate commit.)

Change-Id: I3c03f90dab099e6d3386a235f35b691e7ff671be
Reviewed-on: https://code.wireshark.org/review/3563
Reviewed-by: Daniel Black <danielblack@fedoraproject.org>
Reviewed-by: Evan Huus <eapache@gmail.com>

2 files changed, 18 insertions, 19 deletions

diff --git a/INSTALL b/INSTALL
index 0e563830e8..81899e8a91 100644
--- a/INSTALL
+++ b/INSTALL
@@ -40,7 +40,7 @@ README.windows for those instructions.
    GLib 2.x; you need to configure with --disable-gtk2 to use GTK+
    1.2[.x].
 
-   Please also note that GTK+ 1.2[.x] is only supported up to 
+   Please also note that GTK+ 1.2[.x] is only supported up to
    Wireshark 1.0.x. From Wireshark 1.1.x onwards only GTK+ 2.x
    is supported.
 
@@ -71,7 +71,9 @@ README.windows for those instructions.
 4. Building Wireshark requires Perl (specifically the pod2man program)
    so that the documentation can be built.
 
-5. Run './configure' in the Wireshark distribution directory.
+5. Building Wireshark requires Python.
+
+6. Run './configure' in the Wireshark distribution directory.
    Running './configure --help' displays a complete list of options.
    The file 'INSTALL.configure' contains general instructions for
    using 'configure' and 'make'. Some of the Wireshark non-generic
@@ -208,16 +210,16 @@ README.windows for those instructions.
         Use this switch to change the location where plugins
         are installed.
 
-6. After running './configure', you will see a summary of some
+7. After running './configure', you will see a summary of some
    of the options you chose. Ensure that the summary reflects
    what you want. If it doesn't, re-run './configure' with new options.
 
-7. Run 'make'.  Hopefully, you won't run into any problems.
+8. Run 'make'.  Hopefully, you won't run into any problems.
 
-8. Run './wireshark' or './tshark' or ./dumpcap, and make sure things are
+9. Run './wireshark' or './tshark' or ./dumpcap, and make sure things are
    working. You must have root privileges in order to capture live data.
 
-9./a. Run 'make install'.  If you're running a system that supports
+10./a. Run 'make install'.  If you're running a system that supports
    the RPM, OSX, or System V Release 4 packaging systems, you can
    run one of
 
@@ -229,7 +231,7 @@ README.windows for those instructions.
 
    to make an installable package for your system.
 
-9/b. If you 're running a system that supports APT (Debian/Ubuntu/etc.)
+10/b. If you 're running a system that supports APT (Debian/Ubuntu/etc.)
    run
 
         dpkg-buildpackage -us -uc -rfakeroot
diff --git a/README b/README
index 912be4ccb1..927a74d2e6 100644
--- a/README
+++ b/README
@@ -50,27 +50,24 @@ Wireshark 0.99.4, and Windows 95, 98, and ME are supported by Ethereal 0.99.0.
 
 NOTE: the Makefile appears to depend on GNU "make"; it doesn't appear to
 work with the "make" that comes with Solaris 7 nor the BSD "make".
-Perl is also needed to create the man page.
+
+Both Perl and Python are needed, the former for building the man pages.
 
 If you decide to modify the yacc grammar or lex scanner, then
 you need "flex" - it cannot be built with vanilla "lex" -
 and either "bison" or the Berkeley "yacc". Your flex
 version must be 2.5.1 or greater. Check this with 'flex -V'.
 
-If you decide to modify the NetWare Core Protocol dissector, you
-will need python, as the data for packet types is stored in a python
-script, ncp2222.py.
-
-You must therefore install Perl, GNU "make", "flex", and either "bison" or
-Berkeley "yacc" on systems that lack them.
+You must therefore install Perl, Python, GNU "make", "flex", and either "bison"
+or Berkeley "yacc" on systems that lack them.
 
 Full installation instructions can be found in the INSTALL file.
-         
+
 See also the appropriate README.<OS> files for OS-specific installation
 instructions.
 
 Usage
------          
+-----
 
 In order to capture packets from the network, you need to make the
 dumpcap program set-UID to root, or you need to have access to the
@@ -119,7 +116,7 @@ file if it's small and contains non-sensitive data.
 Support for Lucent/Ascend products is limited to the debug trace output
 generated by the MAX and Pipline series of products.  Wireshark can read
 the output of the "wandsession" "wandisplay", "wannext", and "wdd"
-commands. 
+commands.
 
 Wireshark can also read dump trace output from the Toshiba "Compact Router"
 line of ISDN routers (TR-600 and TR-650). You can telnet to the router
@@ -131,8 +128,8 @@ debug output, get in the diags mode first and then use
 layer-2 category. For more detail how to use these commands, you
 should examine the help command by "layer-2 create ?" or "layer-2 apply ?".
 
-To use the Lucent/Ascend, Toshiba and CoSine traces with Wireshark, you must 
-capture the trace output to a file on disk.  The trace is happening inside 
+To use the Lucent/Ascend, Toshiba and CoSine traces with Wireshark, you must
+capture the trace output to a file on disk.  The trace is happening inside
 the router and the router has no way of saving the trace to a file for you.
 An easy way of doing this under Unix is to run "telnet <ascend> | tee <outfile>".
 Or, if your system has the "script" command installed, you can save