|
Check-in Number:
|
1388 | |
| Date: |
2001-Nov-26 21:08:30 (local)
2001-Nov-26 20:08:30 (UTC) |
| User: | rse |
| Branch: | |
| Comment: |
*** empty log message *** |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/pth/pth.pod 1.148 -> 1.149
--- pth.pod 2001/08/06 17:35:38 1.148
+++ pth.pod 2001/11/26 20:08:30 1.149
@@ -1913,9 +1913,8 @@
| rm -f Makefile
Because B<autoconf> generates additional files, we added a canonical
-C<distclean> target which cleanups this, too. Second, we write
-a (minimalistic) B<autoconf> script specification in a file
-C<configure.in>:
+C<distclean> target which cleans this up. Secondly, we wrote
+C<configure.in>, a (minimal) B<autoconf> script specification:
$ vi configure.in
| AC_INIT(Makefile.in)
@@ -1970,8 +1969,8 @@
Finally let us assume the C<foo> program stays under either a I<GPL> or
I<LGPL> distribution license and we want to make it a stand-alone package for
-easier distribution and installation. That is, we don't want that the
-end-user first has to install B<Pth> just to allow our C<foo> package to
+easier distribution and installation. That is, we don't want to oblige the
+end-user to install B<Pth> just to allow our C<foo> package to
compile. For this, it is a convenient practice to include the required
libraries (here B<Pth>) into the source tree of the package (here C<foo>).
B<Pth> ships with all necessary support to allow us to easily achieve this
|
|
