[ViewVC] Diff of: cvs/App-Staticperl/staticperl.pod

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.20 by root, Fri Dec 10 20:29:17 2010 UTC vs.
Revision 1.21 by root, Sat Dec 11 23:28:22 2010 UTC

 often as necessary.
 =head1 THE F<STATICPERL> SCRIPT
 This module installs a script called F<staticperl> into your perl
-binary directory. The script is fully self-contained, and can be used
+binary directory. The script is fully self-contained, and can be
-without perl (for example, in an uClibc chroot environment). In fact,
+used without perl (for example, in an uClibc chroot environment). In
-it can be extracted from the C<App::Staticperl> distribution tarball as
+fact, it can be extracted from the C<App::Staticperl> distribution
-F<bin/staticperl>, without any installation.
+tarball as F<bin/staticperl>, without any installation. The
+newest (possibly alpha) version can also be downloaded from
+L<http://staticperl.schmorp.de/staticperl>.
 F<staticperl> interprets the first argument as a command to execute,
 optionally followed by any parameters.
 There are two command categories: the "phase 1" commands which deal with
          PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"
       done
    }
 This mostly gains space when linking staticaly, as the functions will
-liekly not be linked in. The gain for dynamically-linked binaries is
+likely not be linked in. The gain for dynamically-linked binaries is
 smaller.
 Also, this leaves C<gethostbyname> in - not only is it actually used
 often, the L<Socket> module also exposes it, so leaving it out usually
 gains little. Why Socket exposes a C function that is in the core already

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines