clean up doc/
diff --git a/doc/python-configure.info b/doc/python-configure.info
--- a/doc/python-configure.info
+++ b/doc/python-configure.info
@@ -1,7 +1,7 @@
-This is python-configure.info, produced by makeinfo version 4.13 from
-/home/brandon/Projects/python-autoconfigure/doc/python-configure.texi.
+This is doc/python-configure.info, produced by makeinfo version 4.13
+from ./doc/python-configure.texi.
-This manual is for python-configure (version 0.1, updated 02 November
+This manual is for python-configure (version 0.1, updated 3 November
2012).
Copyright (C) 2012 Brandon Invergo
@@ -25,7 +25,7 @@ File: python-configure.info, Node: Top,
GNU Source Release Collection
*****************************
-This manual is for python-configure (version 0.1, 02 November 2012).
+This manual is for python-configure (version 0.1, 3 November 2012).
* Menu:
@@ -123,17 +123,18 @@ File: python-configure.info, Node: Usin
2 Using python-configure
************************
-While it is possible to simply copy the python-configure files into
-your project's source directory and use them unmodified, it is
-recommended that you customize them to more appropriately fit your
-needs. In particular, you will want to customize `configure.ac' and
-`Makefile.in'. `configure.ac' contains a series of macros which are
-used by Autoconf to build a portable `configure' shell script. When the
-user invokes `configure', it uses `Makefile.in' as a template to create
-the Make recipe `Makefile'.
+While it is possible to simply copy the python-configure files from the
+`src' directory into your project's source directory and use them
+unmodified, it is recommended that you customize them to more
+appropriately fit your needs. In particular, you will want to customize
+`configure.ac' and `Makefile.in'. `configure.ac' contains a series of
+macros which are used by Autoconf to build a portable `configure' shell
+script. This script either guesses important system settings or is
+provided them by the user. When the user invokes `configure', it uses
+`Makefile.in' as a template to create the Make recipe `Makefile'.
Several Autoconf macros are provided in the python-configure file
-`m4/python.m4' to allow the developer to write robust tests *Note
+`src/m4/python.m4' to allow the developer to write robust tests *Note
Autoconf macros::. Note that when you distribute your software, you
must include this directory and file with your distribution.
@@ -898,17 +899,17 @@ permit their use in free software.
Tag Table:
-Node: Top832
-Node: Introduction1454
-Node: Configuring Python packages2905
-Node: Using python-configure4139
-Node: Required macros5522
-Node: Verifying the Python version6722
-Node: Checking for a module or function9249
-Node: Writing test programs10484
-Node: Using Sphinxbuild to build documentation11593
-Node: Appendix12618
-Node: Autoconf macros12799
-Node: GNU Free Documentation License16502
+Node: Top793
+Node: Introduction1414
+Node: Configuring Python packages2865
+Node: Using python-configure4099
+Node: Required macros5597
+Node: Verifying the Python version6797
+Node: Checking for a module or function9324
+Node: Writing test programs10559
+Node: Using Sphinxbuild to build documentation11668
+Node: Appendix12693
+Node: Autoconf macros12874
+Node: GNU Free Documentation License16577
End Tag Table
diff --git a/doc/python-configure.texi b/doc/python-configure.texi
--- a/doc/python-configure.texi
+++ b/doc/python-configure.texi
@@ -160,18 +160,20 @@ developer is expected to provide proper
@node Using python-configure, Appendix, Introduction, Top
@chapter Using python-configure
-While it is possible to simply copy the python-configure files into
-your project's source directory and use them unmodified, it is
-recommended that you customize them to more appropriately fit your
-needs. In particular, you will want to customize @file{configure.ac}
-and @file{Makefile.in}. @file{configure.ac} contains a series of
-macros which are used by Autoconf to build a portable @file{configure}
-shell script. When the user invokes @file{configure}, it uses
-@file{Makefile.in} as a template to create the Make recipe
+While it is possible to simply copy the python-configure files from
+the @file{src} directory into your project's source directory and use
+them unmodified, it is recommended that you customize them to more
+appropriately fit your needs. In particular, you will want to
+customize @file{configure.ac} and
+@file{Makefile.in}. @file{configure.ac} contains a series of macros
+which are used by Autoconf to build a portable @file{configure} shell
+script. This script either guesses important system settings or is
+provided them by the user. When the user invokes @file{configure}, it
+uses @file{Makefile.in} as a template to create the Make recipe
@file{Makefile}.
Several Autoconf macros are provided in the python-configure file
-@file{m4/python.m4} to allow the developer to write robust tests
+@file{src/m4/python.m4} to allow the developer to write robust tests
@xref{Autoconf macros}. Note that when you distribute your software,
you must include this directory and file with your distribution.
diff --git a/doc/stamp-vti b/doc/stamp-vti
new file mode 100644
--- /dev/null
+++ b/doc/stamp-vti
@@ -0,0 +1,4 @@
+@set UPDATED 3 November 2012
+@set UPDATED-MONTH November 2012
+@set EDITION 0.1
+@set VERSION 0.1
diff --git a/doc/version.texi b/doc/version.texi
--- a/doc/version.texi
+++ b/doc/version.texi
@@ -1,4 +1,4 @@
-@set UPDATED 02 November 2012
+@set UPDATED 3 November 2012
@set UPDATED-MONTH November 2012
@set EDITION 0.1
@set VERSION 0.1