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

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.28 by root, Tue Dec 21 19:44:43 2010 UTC vs.
Revision 1.31 by root, Thu Dec 23 14:16:25 2010 UTC

 that are added automatically. Only one (F<.packlist> files) is currently
 optional and can be influenced, the others are always included:
 =over 4
-=item C<--usepacklist>
+=item C<--usepacklists>
 Read F<.packlist> files for each distribution that happens to match a
 module name you specified. Sounds weird, and it is, so expect semantics to
 change somehow in the future.
 =item Patterns not starting with F</> will be anchored at the end of the path.
 That is, F<idna.pl> will match any file called F<idna.pl> anywhere in the
 hierarchy, but not any directories of the same name.
-=item A F<*> matches any single component.
+=item A F<*> matches anything within a single path component.
 That is, F</unicore/*.pl> would match all F<.pl> files directly inside
 C</unicore>, not any deeper level F<.pl> files. Or in other words, F<*>
 will not match slashes.
 Returns the list of all paths embedded in this binary.
 =back
-=head1 FULLY STATIC BINARIES - BUILDROOT
+=head1 FULLY STATIC BINARIES - UCLIBC AND BUILDROOT
 To make truly static (Linux-) libraries, you might want to have a look at
 buildroot (L<http://buildroot.uclibc.org/>).
 Buildroot is primarily meant to set up a cross-compile environment (which
 handling for those files), so including them on demand by your application
 only might pay off.
 To simply include the whole unicode database, use:
-   --incglob '/unicore/*.pl'
+   --incglob '/unicore/**.pl'
 =item AnyEvent
 AnyEvent needs a backend implementation that it will load in a delayed
 fashion. The L<AnyEvent::Impl::Perl> backend is the default choice
 If you want to handle IRIs or IDNs (L<AnyEvent::Util> punycode and idn
 functions), you also need to include C<"AnyEvent/Util/idna.pl"> and
 C<"AnyEvent/Util/uts46data.pl">.
-Or you can use C<--usepacklist> and specify C<-MAnyEvent> to include
+Or you can use C<--usepacklists> and specify C<-MAnyEvent> to include
 everything.
 =item Carp
 Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of
 turn might need L<"Config_heavy.pl">. Including the latter gives you
 both.
 =item Term::ReadLine::Perl
-Also needs L<Term::ReadLine::readline>, or C<--usepacklist>.
+Also needs L<Term::ReadLine::readline>, or C<--usepacklists>.
 =item URI
 URI implements schemes as separate modules - the generic URL scheme is
 implemented in L<URI::_generic>, HTTP is implemented in L<URI::http>. If
 you need to use any of these schemes, you should include these manually,
-or use C<--usepacklist>.
+or use C<--usepacklists>.
 =back
 =head2 RECIPES
 =over 4
-=item Linking everything in
+=item Just link everything in
 To link just about everything installed in the perl library into a new
-perl, try this:
+perl, try this (the first time this runs it will take a long time, as a
+lot of files need to be parsed):
-   staticperl mkperl --strip ppi --incglob '*'
+   staticperl mkperl -v --strip ppi --incglob '*'
+If you don't mind the extra megabytes, this can be a very effective way of
+creating bundles without having to worry about forgetting any modules.
+You get even more useful variants of this method by first selecting
+everything, and then excluding stuff you are reasonable sure not to need -
+L<bigperl|http://staticperl.schmorp.de/bigperl.html> uses this approach.
-=item Getting rid of netdb function
+=item Getting rid of netdb functions
 The perl core has lots of netdb functions (C<getnetbyname>, C<getgrent>
 and so on) that few applications use. You can avoid compiling them in by
 putting the following fragment into a C<preconfigure> hook:
       do
          PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"
       done
    }
-This mostly gains space when linking staticaly, as the functions will
+This mostly gains space when linking statically, as the functions will
 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

Diff Legend

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

Comparing App-Staticperl/staticperl.pod (file contents): Revision 1.28 by root, Tue Dec 21 19:44:43 2010 UTC vs. Revision 1.31 by root, Thu Dec 23 14:16:25 2010 UTC

Diff Legend

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.28 by root, Tue Dec 21 19:44:43 2010 UTC vs.
Revision 1.31 by root, Thu Dec 23 14:16:25 2010 UTC