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

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.27 by root, Tue Dec 21 19:32:34 2010 UTC vs.
Revision 1.48 by root, Sun Jul 10 01:37:56 2011 UTC

…		…
9	staticperl configure # fetch and then configure perl	9	staticperl configure # fetch and then configure perl
10	staticperl build # configure and then build perl	10	staticperl build # configure and then build perl
11	staticperl install # build and then install perl	11	staticperl install # build and then install perl
12	staticperl clean # clean most intermediate files (restart at configure)	12	staticperl clean # clean most intermediate files (restart at configure)
13	staticperl distclean # delete everything installed by this script	13	staticperl distclean # delete everything installed by this script
		14	staticperl perl ... # invoke the perlinterpreter
14	staticperl cpan # invoke CPAN shell	15	staticperl cpan # invoke CPAN shell
15	staticperl instmod path... # install unpacked modules	16	staticperl instmod path... # install unpacked modules
16	staticperl instcpan modulename... # install modules from CPAN	17	staticperl instcpan modulename... # install modules from CPAN
17	staticperl mkbundle <bundle-args...> # see documentation	18	staticperl mkbundle <bundle-args...> # see documentation
18	staticperl mkperl <bundle-args...> # see documentation	19	staticperl mkperl <bundle-args...> # see documentation
…		…
20		21
21	Typical Examples:	22	Typical Examples:
22		23
23	staticperl install # fetch, configure, build and install perl	24	staticperl install # fetch, configure, build and install perl
24	staticperl cpan # run interactive cpan shell	25	staticperl cpan # run interactive cpan shell
25	staticperl mkperl -M '"Config_heavy.pl"' # build a perl that supports -V	26	staticperl mkperl -MConfig_heavy.pl # build a perl that supports -V
26	staticperl mkperl -MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI -MURI::http	27	staticperl mkperl -MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI -MURI::http
27	# build a perl with the above modules linked in	28	# build a perl with the above modules linked in
28	staticperl mkapp myapp --boot mainprog mymodules	29	staticperl mkapp myapp --boot mainprog mymodules
29	# build a binary "myapp" from mainprog and mymodules	30	# build a binary "myapp" from mainprog and mymodules
30		31
…		…
38	file that contains perl interpreter, libc, all the modules you need, all	39	file that contains perl interpreter, libc, all the modules you need, all
39	the libraries you need and of course your actual program.	40	the libraries you need and of course your actual program.
40		41
41	With F<uClibc> and F<upx> on x86, you can create a single 500kb binary	42	With F<uClibc> and F<upx> on x86, you can create a single 500kb binary
42	that contains perl and 100 modules such as POSIX, AnyEvent, EV, IO::AIO,	43	that contains perl and 100 modules such as POSIX, AnyEvent, EV, IO::AIO,
43	Coro and so on. Or any other choice of modules.	44	Coro and so on. Or any other choice of modules (and some other size :).
44		45
45	To see how this turns out, you can try out smallperl and bigperl, two	46	To see how this turns out, you can try out smallperl and bigperl, two
46	pre-built static and compressed perl binaries with many and even more	47	pre-built static and compressed perl binaries with many and even more
47	modules: just follow the links at L<http://staticperl.schmorp.de/>.	48	modules: just follow the links at L<http://staticperl.schmorp.de/>.
48		49
…		…
83	With F<staticperl>, the burden is mostly with the developer - only direct	84	With F<staticperl>, the burden is mostly with the developer - only direct
84	compile-time dependencies and L<AutoLoader> are handled automatically.	85	compile-time dependencies and L<AutoLoader> are handled automatically.
85	This means the modules to include often need to be tweaked manually.	86	This means the modules to include often need to be tweaked manually.
86		87
87	All this does not preclude more permissive modes to be implemented in	88	All this does not preclude more permissive modes to be implemented in
88	the future, but right now, you have to resolve state hidden dependencies	89	the future, but right now, you have to resolve hidden dependencies
89	manually.	90	manually.
90		91
91	=item * PAR works out of the box, F<staticperl> does not.	92	=item * PAR works out of the box, F<staticperl> does not.
92		93
93	Maintaining your own custom perl build can be a pain in the ass, and while	94	Maintaining your own custom perl build can be a pain in the ass, and while
…		…
139	with creating binaries and bundle files.	140	with creating binaries and bundle files.
140		141
141	=head2 PHASE 1 COMMANDS: INSTALLING PERL	142	=head2 PHASE 1 COMMANDS: INSTALLING PERL
142		143
143	The most important command is F<install>, which does basically	144	The most important command is F<install>, which does basically
144	everything. The default is to download and install perl 5.12.2 and a few	145	everything. The default is to download and install perl 5.12.3 and a few
145	modules required by F<staticperl> itself, but all this can (and should) be	146	modules required by F<staticperl> itself, but all this can (and should) be
146	changed - see L<CONFIGURATION>, below.	147	changed - see L<CONFIGURATION>, below.
147		148
148	The command	149	The command
149		150
…		…
186	=item F<staticperl install>	187	=item F<staticperl install>
187		188
188	Wipes the perl installation directory (usually F<~/.staticperl/perl>) and	189	Wipes the perl installation directory (usually F<~/.staticperl/perl>) and
189	installs the perl distribution, potentially after building it first.	190	installs the perl distribution, potentially after building it first.
190		191
		192	=item F<staticperl perl> [args...]
		193
		194	Invokes the compiled perl interpreter with the given args. Basically the
		195	same as starting perl directly (usually via F<~/.staticperl/bin/perl>),
		196	but beats typing the path sometimes.
		197
		198	Example: check that the Gtk2 module is installed and loadable.
		199
		200	staticperl perl -MGtk2 -e0
		201
191	=item F<staticperl cpan> [args...]	202	=item F<staticperl cpan> [args...]
192		203
193	Starts an interactive CPAN shell that you can use to install further	204	Starts an interactive CPAN shell that you can use to install further
194	modules. Installs the perl first if necessary, but apart from that,	205	modules. Installs the perl first if necessary, but apart from that,
195	no magic is involved: you could just as well run it manually via	206	no magic is involved: you could just as well run it manually via
196	F<~/.staticperl/perl/bin/cpan>.	207	F<~/.staticperl/perl/bin/cpan>, except that F<staticperl> additionally
		208	sets the environment variable C<$PERL> to the path of the perl
		209	interpreter, which is handy in subshells.
197		210
198	Any additional arguments are simply passed to the F<cpan> command.	211	Any additional arguments are simply passed to the F<cpan> command.
199		212
200	=item F<staticperl instcpan> module...	213	=item F<staticperl instcpan> module...
201		214
…		…
252		265
253	# first make sure we have perl and the required modules	266	# first make sure we have perl and the required modules
254	staticperl instcpan AnyEvent::HTTPD	267	staticperl instcpan AnyEvent::HTTPD
255		268
256	# now build the perl	269	# now build the perl
257	staticperl mkperl -M'"Config_heavy.pl"' -MAnyEvent::Impl::Perl \	270	staticperl mkperl -MConfig_heavy.pl -MAnyEvent::Impl::Perl \
258	-MAnyEvent::HTTPD -MURI::http \	271	-MAnyEvent::HTTPD -MURI::http \
259	--add 'eg/httpd httpd.pm'	272	--add 'eg/httpd httpd.pm'
260		273
261	# finally, invoke it	274	# finally, invoke it
262	./perl -Mhttpd	275	./perl -Mhttpd
…		…
381		394
382	=over 4	395	=over 4
383		396
384	=item C<--use> F<module> \| C<-M>F<module>	397	=item C<--use> F<module> \| C<-M>F<module>
385		398
386	Include the named module and trace direct dependencies. This is done by	399	Include the named module or perl library and trace direct
387	C<require>'ing the module in a subprocess and tracing which other modules	400	dependencies. This is done by loading the module in a subprocess and
388	and files it actually loads.	401	tracing which other modules and files it actually loads.
389		402
390	Example: include AnyEvent and AnyEvent::Impl::Perl.	403	Example: include AnyEvent and AnyEvent::Impl::Perl.
391		404
392	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl	405	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl
393		406
394	Sometimes you want to load old-style "perl libraries" (F<.pl> files), or	407	Sometimes you want to load old-style "perl libraries" (F<.pl> files), or
395	maybe other weirdly named files. To do that, you need to quote the name in	408	maybe other weirdly named files. To support this, the C<--use> option
396	single or double quotes. When given on the command line, you probably need	409	actually tries to do what you mean, depending on the string you specify:
397	to quote once more to avoid your shell interpreting it. Common cases that	410
398	need this are F<Config_heavy.pl> and F<utf8_heavy.pl>.	411	=over 4
		412
		413	=item a possibly valid module name, e.g. F<common::sense>, F<Carp>,
		414	F<Coro::Mysql>.
		415
		416	If the string contains no quotes, no F</> and no F<.>, then C<--use>
		417	assumes that it is a normal module name. It will create a new package and
		418	evaluate a C<use module> in it, i.e. it will load the package and do a
		419	default import.
		420
		421	The import step is done because many modules trigger more dependencies
		422	when something is imported than without.
		423
		424	=item anything that contains F</> or F<.> characters,
		425	e.g. F<utf8_heavy.pl>, F<Module/private/data.pl>.
		426
		427	The string will be quoted and passed to require, as if you used C<require
		428	$module>. Nothing will be imported.
		429
		430	=item "path" or 'path', e.g. C<"utf8_heavy.pl">.
		431
		432	If you enclose the name into single or double quotes, then the quotes will
		433	be removed and the resulting string will be passed to require. This syntax
		434	is form compatibility with older versions of staticperl and should not be
		435	used anymore.
		436
		437	=back
		438
		439	Example: C<use> AnyEvent::Socket, once using C<use> (importing the
		440	symbols), and once via C<require>, not importing any symbols. The first
		441	form is preferred as many modules load some extra dependencies when asked
		442	to export symbols.
		443
		444	staticperl mkbundle -MAnyEvent::Socket # use + import
		445	staticperl mkbundle -MAnyEvent/Socket.pm # require only
399		446
400	Example: include the required files for F<perl -V> to work in all its	447	Example: include the required files for F<perl -V> to work in all its
401	glory (F<Config.pm> is included automatically by this).	448	glory (F<Config.pm> is included automatically by the dependency tracker).
402		449
403	# bourne shell	450	# shell command
404	staticperl mkbundle --use '"Config_heavy.pl"'	451	staticperl mkbundle -MConfig_heavy.pl
405		452
406	# bundle specification file	453	# bundle specification file
407	use "Config_heavy.pl"	454	use Config_heavy.pl
408		455
409	The C<-M>module syntax is included as an alias that might be easier to	456	The C<-M>module syntax is included as a convenience that might be easier
410	remember than C<--use>. Or maybe it confuses people. Time will tell. Or	457	to remember than C<--use> - it's the same switch as perl itself uses
		458	to load modules. Or maybe it confuses people. Time will tell. Or maybe
411	maybe not. Sigh.	459	not. Sigh.
412		460
413	=item C<--eval> "perl code" \| C<-e> "perl code"	461	=item C<--eval> "perl code" \| C<-e> "perl code"
414		462
415	Sometimes it is easier (or necessary) to specify dependencies using perl	463	Sometimes it is easier (or necessary) to specify dependencies using perl
416	code, or maybe one of the modules you use need a special use statement. In	464	code, or maybe one of the modules you use need a special use statement. In
417	that case, you can use C<--eval> to execute some perl snippet or set some	465	that case, you can use C<--eval> to execute some perl snippet or set some
418	variables or whatever you need. All files C<require>'d or C<use>'d while	466	variables or whatever you need. All files C<require>'d or C<use>'d while
419	executing the snippet are included in the final bundle.	467	executing the snippet are included in the final bundle.
420		468
421	Keep in mind that F<mkbundle> will only C<require> the modules named	469	Keep in mind that F<mkbundle> will not import any symbols from the modules
422	by the C<--use> option, so do not expect the symbols from modules you	470	named by the C<--use> option, so do not expect the symbols from modules
423	C<--use>'d earlier on the command line to be available.	471	you C<--use>'d earlier on the command line to be available.
424		472
425	Example: force L<AnyEvent> to detect a backend and therefore include it	473	Example: force L<AnyEvent> to detect a backend and therefore include it
426	in the final bundle.	474	in the final bundle.
427		475
428	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'	476	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'
…		…
455	This is very useful to include "everything":	503	This is very useful to include "everything":
456		504
457	--incglob '*'	505	--incglob '*'
458		506
459	It is also useful for including perl libraries, or trees of those, such as	507	It is also useful for including perl libraries, or trees of those, such as
460	the unicode database files needed by some perl builtins, the regex engine	508	the unicode database files needed by some perl built-ins, the regex engine
461	and other modules.	509	and other modules.
462		510
463	--incglob '/unicore/**.pl'	511	--incglob '/unicore/**.pl'
464		512
465	=item C<--add> F<file> \| C<--add> "F<file> alias"	513	=item C<--add> F<file> \| C<--add> "F<file> alias"
466		514
467	Adds the given (perl) file into the bundle (and optionally call it	515	Adds the given (perl) file into the bundle (and optionally call it
468	"alias"). The F<file> is either an absolute path or a path relative to	516	"alias"). The F<file> is either an absolute path or a path relative to the
469	the current directory. If an alias is specified, then this is the name it	517	current directory. If an alias is specified, then this is the name it will
470	will use for C<@INC> searches, otherfile the F<file> will be used as the	518	use for C<@INC> searches, otherwise the path F<file> will be used as the
471	internal name.	519	internal name.
472		520
473	This switch is used to include extra files into the bundle.	521	This switch is used to include extra files into the bundle.
474		522
475	Example: embed the file F<httpd> in the current directory as F<httpd.pm>	523	Example: embed the file F<httpd> in the current directory as F<httpd.pm>
476	when creating the bundle.	524	when creating the bundle.
477		525
478	staticperl mkperl --add "httpd httpd.pm"	526	staticperl mkperl --add "httpd httpd.pm"
		527
		528	# can be accessed via "use httpd"
		529
		530	Example: add a file F<initcode> from the current directory.
		531
		532	staticperl mkperl --add 'initcode &initcode'
		533
		534	# can be accessed via "do '&initcode'"
479		535
480	Example: add local files as extra modules in the bundle.	536	Example: add local files as extra modules in the bundle.
481		537
482	# specification file	538	# specification file
483	add file1 myfiles/file1.pm	539	add file1 myfiles/file1.pm
…		…
493		549
494	Just like C<--add>, except that it treats the file as binary and adds it	550	Just like C<--add>, except that it treats the file as binary and adds it
495	without any postprocessing (perl files might get stripped to reduce their	551	without any postprocessing (perl files might get stripped to reduce their
496	size).	552	size).
497		553
498	You should probably add a C</> prefix to avoid clashing with embedded perl	554	If you specify an alias you should probably add a C</> prefix to avoid
499	files (whose paths do not start with C</>), and/or use a special directory	555	clashing with embedded perl files (whose paths never start with C</>),
500	prefix, such as C</res/name>.	556	and/or use a special directory prefix, such as C</res/name>.
501		557
502	You can later get a copy of these files by calling C<staticperl::find	558	You can later get a copy of these files by calling C<staticperl::find
503	"alias">.	559	"alias">.
504		560
505	An alternative way to embed binary files is to convert them to perl and	561	An alternative way to embed binary files is to convert them to perl and
506	use C<do> to get the contents - this method is a bit cumbersome, but works	562	use C<do> to get the contents - this method is a bit cumbersome, but works
507	both inside and outside of a staticperl bundle:	563	both inside and outside of a staticperl bundle, without extra ado:
508		564
509	# a "binary" file, call it "bindata.pl"	565	# a "binary" file, call it "bindata.pl"
510	<<'SOME_MARKER'	566	<<'SOME_MARKER'
511	binary data NOT containing SOME_MARKER	567	binary data NOT containing SOME_MARKER
512	SOME_MARKER	568	SOME_MARKER
513		569
514	# load the binary	570	# load the binary
515	chomp (my $data = do "bindata.pl");	571	chomp (my $data = do "bindata.pl");
516		572
		573	=item C<--allow-dynamic>
		574
		575	By default, when F<mkbundle> hits a dynamic perl extension (e.g. a F<.so>
		576	or F<.dll> file), it will stop with a fatal error.
		577
		578	When this option is enabled, F<mkbundle> packages the shared
		579	object into the bundle instead, with a prefix of F<!>
		580	(e.g. F<!auto/List/Util/Util.so>). What you do with that is currently up
		581	to you, F<staticperl> has no special support for this at the moment, apart
		582	from working around the lack of availability of F<PerlIO::scalar> while
		583	bootstrapping, at a speed cost.
		584
		585	One way to deal with this is to write all files starting with F<!> into
		586	some directory and then C<unshift> that path onto C<@INC>.
		587
		588	#TODO: example
		589
517	=back	590	=back
518		591
519	=item Step 2: filter all files using C<--include> and C<--exclude> options.	592	=item Step 2: filter all files using C<--include> and C<--exclude> options.
520		593
521	After all candidate files and modules are added, they are I<filtered>	594	After all candidate files and modules are added, they are I<filtered>
522	by a combination of C<--include> and C<--exclude> patterns (there is an	595	by a combination of C<--include> and C<--exclude> patterns (there is an
523	implicit C<--include **> at the end, so if no filters are specified, all	596	implicit C<--include *> at the end, so if no filters are specified, all
524	files are included).	597	files are included).
525		598
526	All that this step does is potentially reduce the number of files that are	599	All that this step does is potentially reduce the number of files that are
527	to be included - no new files are added during this step.	600	to be included - no new files are added during this step.
528		601
…		…
553	that are added automatically. Only one (F<.packlist> files) is currently	626	that are added automatically. Only one (F<.packlist> files) is currently
554	optional and can be influenced, the others are always included:	627	optional and can be influenced, the others are always included:
555		628
556	=over 4	629	=over 4
557		630
558	=item C<--usepacklist>	631	=item C<--usepacklists>
559		632
560	Read F<.packlist> files for each distribution that happens to match a	633	Read F<.packlist> files for each distribution that happens to match a
561	module name you specified. Sounds weird, and it is, so expect semantics to	634	module name you specified. Sounds weird, and it is, so expect semantics to
562	change somehow in the future.	635	change somehow in the future.
563		636
…		…
631	Last not least, if you need accurate line numbers in error messages,	704	Last not least, if you need accurate line numbers in error messages,
632	or in the unlikely case where C<pod> is too slow, or some module gets	705	or in the unlikely case where C<pod> is too slow, or some module gets
633	mistreated, you can specify C<none> to not mangle included perl sources in	706	mistreated, you can specify C<none> to not mangle included perl sources in
634	any way.	707	any way.
635		708
636	=item --perl	709	=item C<--perl>
637		710
638	After writing out the bundle files, try to link a new perl interpreter. It	711	After writing out the bundle files, try to link a new perl interpreter. It
639	will be called F<perl> and will be left in the current working	712	will be called F<perl> and will be left in the current working
640	directory. The bundle files will be removed.	713	directory. The bundle files will be removed.
641		714
…		…
646	it will be even smaller than the standard perl interpreter as none of the	719	it will be even smaller than the standard perl interpreter as none of the
647	modules of the base distribution (such as L<Fcntl>) will be included.	720	modules of the base distribution (such as L<Fcntl>) will be included.
648		721
649	staticperl mkperl -Mcommon::sense	722	staticperl mkperl -Mcommon::sense
650		723
651	=item --app name	724	=item C<--app> F<name>
652		725
653	After writing out the bundle files, try to link a new standalone	726	After writing out the bundle files, try to link a new standalone
654	program. It will be called C<name>, and the bundle files get removed after	727	program. It will be called C<name>, and the bundle files get removed after
655	linking it.	728	linking it.
656		729
…		…
660	The difference to the (mutually exclusive) C<--perl> option is that the	733	The difference to the (mutually exclusive) C<--perl> option is that the
661	binary created by this option will not try to act as a perl interpreter -	734	binary created by this option will not try to act as a perl interpreter -
662	instead it will simply initialise the perl interpreter, clean it up and	735	instead it will simply initialise the perl interpreter, clean it up and
663	exit.	736	exit.
664		737
665	This means that, by default, it will do nothing but burna few CPU cycles	738	This means that, by default, it will do nothing but burn a few CPU cycles
666	- for it to do something useful you I<must> add some boot code, e.g. with	739	- for it to do something useful you I<must> add some boot code, e.g. with
667	the C<--boot> option.	740	the C<--boot> option.
668		741
669	Example: create a standalone perl binary called F<./myexe> that will	742	Example: create a standalone perl binary called F<./myexe> that will
670	execute F<appfile> when it is started.	743	execute F<appfile> when it is started.
671		744
672	staticperl mkbundle --app myexe --boot appfile	745	staticperl mkbundle --app myexe --boot appfile
673		746
		747	=item C<--ignore-env>
		748
		749	Generates extra code to unset some environment variables before
		750	initialising/running perl. Perl supports a lot of environment variables
		751	that might alter execution in ways that might be undesirablre for
		752	standalone applications, and this option removes those known to cause
		753	trouble.
		754
		755	Specifically, these are removed:
		756
		757	C<PERL_HASH_SEED_DEBUG> and C<PERL_DEBUG_MSTATS> can cause underaible
		758	output, C<PERL5OPT>, C<PERL_DESTRUCT_LEVEL>, C<PERL_HASH_SEED> and
		759	C<PERL_SIGNALS> can alter execution significantly, and C<PERL_UNICODE>,
		760	C<PERLIO_DEBUG> and C<PERLIO> can affect input and output.
		761
		762	The variables C<PERL_LIB> and C<PERL5_LIB> are always ignored because the
		763	startup code used by F<staticperl> overrides C<@INC> in all cases.
		764
		765	This option will not make your program more secure (unless you are
		766	running with elevated privileges), but it will reduce the surprise effect
		767	when a user has these environment variables set and doesn't expect your
		768	standalone program to act like a perl interpreter.
		769
674	=item --static	770	=item C<--static>
675		771
676	Add C<-static> to F<bundle.ldopts>, which means a fully static (if	772	Add C<-static> to F<bundle.ldopts>, which means a fully static (if
677	supported by the OS) executable will be created. This is not immensely	773	supported by the OS) executable will be created. This is not immensely
678	useful when just creating the bundle files, but is most useful when	774	useful when just creating the bundle files, but is most useful when
679	linking a binary with the C<--perl> or C<--app> options.	775	linking a binary with the C<--perl> or C<--app> options.
…		…
686	systems based on GNU libc don't really support it in a very usable	782	systems based on GNU libc don't really support it in a very usable
687	fashion either. Try uClibc if you want to create fully statically linked	783	fashion either. Try uClibc if you want to create fully statically linked
688	executables, or try the C<--staticlib> option to link only some libraries	784	executables, or try the C<--staticlib> option to link only some libraries
689	statically.	785	statically.
690		786
691	=item --staticlib libname	787	=item C<--staticlib> libname
692		788
693	When not linking fully statically, this option allows you to link specific	789	When not linking fully statically, this option allows you to link specific
694	libraries statically. What it does is simply replace all occurances of	790	libraries statically. What it does is simply replace all occurrences of
695	C<-llibname> with the GCC-specific C<-Wl,-Bstatic -llibname -Wl,-Bdynamic>	791	C<-llibname> with the GCC-specific C<-Wl,-Bstatic -llibname -Wl,-Bdynamic>
696	option.	792	option.
697		793
698	This will have no effect unless the library is actually linked against,	794	This will have no effect unless the library is actually linked against,
699	specifically, C<--staticlib> will not link against the named library	795	specifically, C<--staticlib> will not link against the named library
700	unless it would be linked against anyway.	796	unless it would be linked against anyway.
701		797
702	Example: link libcrypt statically into the binary.	798	Example: link libcrypt statically into the final binary.
703		799
704	staticperl mkperl -MIO::AIO --staticlib crypt	800	staticperl mkperl -MIO::AIO --staticlib crypt
705		801
706	# ldopts might now contain:	802	# ldopts might now contain:
707	# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread	803	# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread
…		…
728	=item Patterns not starting with F</> will be anchored at the end of the path.	824	=item Patterns not starting with F</> will be anchored at the end of the path.
729		825
730	That is, F<idna.pl> will match any file called F<idna.pl> anywhere in the	826	That is, F<idna.pl> will match any file called F<idna.pl> anywhere in the
731	hierarchy, but not any directories of the same name.	827	hierarchy, but not any directories of the same name.
732		828
733	=item A F<*> matches any single component.	829	=item A F<*> matches anything within a single path component.
734		830
735	That is, F</unicore/*.pl> would match all F<.pl> files directly inside	831	That is, F</unicore/*.pl> would match all F<.pl> files directly inside
736	C</unicore>, not any deeper level F<.pl> files. Or in other words, F<*>	832	C</unicore>, not any deeper level F<.pl> files. Or in other words, F<*>
737	will not match slashes.	833	will not match slashes.
738		834
…		…
805	=item C<STATICPERL>	901	=item C<STATICPERL>
806		902
807	The directory where staticperl stores all its files	903	The directory where staticperl stores all its files
808	(default: F<~/.staticperl>).	904	(default: F<~/.staticperl>).
809		905
		906	=item C<DLCACHE>
		907
		908	The path to a directory (will be created if it doesn't exist) where
		909	downloaded perl sources are being cached, to avoid downloading them
		910	again. The default is empty, which means there is no cache.
		911
		912	=item C<PERL_VERSION>
		913
		914	The perl version to install - default is currently C<5.12.3>, but C<5.8.9>
		915	is also a good choice (5.8.9 is much smaller than 5.12.3, while 5.10.1 is
		916	about as big as 5.12.3).
		917
810	=item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ...	918	=item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ...
811		919
812	Usually set to C<1> to make modules "less inquisitive" during their	920	Usually set to C<1> to make modules "less inquisitive" during their
813	installation, you can set any environment variable you want - some modules	921	installation. You can set (and export!) any environment variable you want
814	(such as L<Coro> or L<EV>) use environment variables for further tweaking.	922	- some modules (such as L<Coro> or L<EV>) use environment variables for
815		923	further tweaking.
816	=item C<PERL_VERSION>
817
818	The perl version to install - default is currently C<5.12.2>, but C<5.8.9>
819	is also a good choice (5.8.9 is much smaller than 5.12.2, while 5.10.1 is
820	about as big as 5.12.2).
821		924
822	=item C<PERL_PREFIX>	925	=item C<PERL_PREFIX>
823		926
824	The prefix where perl gets installed (default: F<$STATICPERL/perl>),	927	The prefix where perl gets installed (default: F<$STATICPERL/perl>),
825	i.e. where the F<bin> and F<lib> subdirectories will end up.	928	i.e. where the F<bin> and F<lib> subdirectories will end up.
…		…
846	F<~/.staticperlrc> to override them.	949	F<~/.staticperlrc> to override them.
847		950
848	Most of the variables override (or modify) the corresponding F<Configure>	951	Most of the variables override (or modify) the corresponding F<Configure>
849	variable, except C<PERL_CCFLAGS>, which gets appended.	952	variable, except C<PERL_CCFLAGS>, which gets appended.
850		953
		954	You should have a look near the beginning of the F<staticperl> script -
		955	staticperl tries to default C<PERL_OPTIMIZE> to some psace-saving options
		956	suitable for newer gcc versions. For other compilers or older versions you
		957	need to adjust these, for example, in your F<~/.staticperlrc>.
		958
851	=back	959	=back
852		960
853	=head4 Variables you probably I<do not want> to override	961	=head4 Variables you probably I<do not want> to override
854		962
855	=over 4	963	=over 4
…		…
873	=head3 OVERRIDABLE HOOKS	981	=head3 OVERRIDABLE HOOKS
874		982
875	In addition to environment variables, it is possible to provide some	983	In addition to environment variables, it is possible to provide some
876	shell functions that are called at specific times. To provide your own	984	shell functions that are called at specific times. To provide your own
877	commands, just define the corresponding function.	985	commands, just define the corresponding function.
		986
		987	The actual order in which hooks are invoked during a full install
		988	from scratch is C<preconfigure>, C<patchconfig>, C<postconfigure>,
		989	C<postbuild>, C<postinstall>.
878		990
879	Example: install extra modules from CPAN and from some directories	991	Example: install extra modules from CPAN and from some directories
880	at F<staticperl install> time.	992	at F<staticperl install> time.
881		993
882	postinstall() {	994	postinstall() {
…		…
889		1001
890	=over 4	1002	=over 4
891		1003
892	=item preconfigure	1004	=item preconfigure
893		1005
894	Called just before running F<./Configur> in the perl source	1006	Called just before running F<./Configure> in the perl source
895	directory. Current working directory is the perl source directory.	1007	directory. Current working directory is the perl source directory.
896		1008
897	This can be used to set any C<PERL_xxx> variables, which might be costly	1009	This can be used to set any C<PERL_xxx> variables, which might be costly
898	to compute.	1010	to compute.
899		1011
		1012	=item patchconfig
		1013
		1014	Called after running F<./Configure> in the perl source directory to create
		1015	F<./config.sh>, but before running F<./Configure -S> to actually apply the
		1016	config. Current working directory is the perl source directory.
		1017
		1018	Can be used to tailor/patch F<config.sh> or do any other modifications.
		1019
900	=item postconfigure	1020	=item postconfigure
901		1021
902	Called after configuring, but before building perl. Current working	1022	Called after configuring, but before building perl. Current working
903	directory is the perl source directory.	1023	directory is the perl source directory.
904
905	Could be used to tailor/patch config.sh (followed by F<sh Configure -S>)
906	or do any other modifications.
907		1024
908	=item postbuild	1025	=item postbuild
909		1026
910	Called after building, but before installing perl. Current working	1027	Called after building, but before installing perl. Current working
911	directory is the perl source directory.	1028	directory is the perl source directory.
…		…
949	A header file that contains the prototypes of the few symbols "exported"	1066	A header file that contains the prototypes of the few symbols "exported"
950	by bundle.c, and also exposes the perl headers to the application.	1067	by bundle.c, and also exposes the perl headers to the application.
951		1068
952	=over 4	1069	=over 4
953		1070
954	=item staticperl_init ()	1071	=item staticperl_init (xs_init = 0)
955		1072
956	Initialises the perl interpreter. You can use the normal perl functions	1073	Initialises the perl interpreter. You can use the normal perl functions
957	after calling this function, for example, to define extra functions or	1074	after calling this function, for example, to define extra functions or
958	to load a .pm file that contains some initialisation code, or the main	1075	to load a .pm file that contains some initialisation code, or the main
959	program function:	1076	program function:
…		…
966	}	1083	}
967		1084
968	static void	1085	static void
969	run_myapp(void)	1086	run_myapp(void)
970	{	1087	{
971	staticperl_init ();	1088	staticperl_init (0);
972	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");	1089	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");
973	eval_pv ("require myapp::main", 1); // executes "myapp/main.pm"	1090	eval_pv ("require myapp::main", 1); // executes "myapp/main.pm"
974	}	1091	}
975		1092
		1093	When your bootcode already wants to access some XS functions at
		1094	compiletime, then you need to supply an C<xs_init> function pointer that
		1095	is called as soon as perl is initialised enough to define XS functions,
		1096	but before the preamble code is executed:
		1097
		1098	static void
		1099	xs_init (pTHX)
		1100	{
		1101	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");
		1102	}
		1103
		1104	static void
		1105	run_myapp(void)
		1106	{
		1107	staticperl_init (xs_init);
		1108	}
		1109
		1110	=item staticperl_cleanup ()
		1111
		1112	In the unlikely case that you want to destroy the perl interpreter, here
		1113	is the corresponding function.
		1114
976	=item staticperl_xs_init (pTHX)	1115	=item staticperl_xs_init (pTHX)
977		1116
978	Sometimes you need direct control over C<perl_parse> and C<perl_run>, in	1117	Sometimes you need direct control over C<perl_parse> and C<perl_run>, in
979	which case you do not want to use C<staticperl_init> but call them on your	1118	which case you do not want to use C<staticperl_init> but call them on your
980	own.	1119	own.
981		1120
982	Then you need this function - either pass it directly as the C<xs_init>	1121	Then you need this function - either pass it directly as the C<xs_init>
983	function to C<perl_parse>, or call it from your own C<xs_init> function.	1122	function to C<perl_parse>, or call it as one of the first things from your
984		1123	own C<xs_init> function.
985	=item staticperl_cleanup ()
986
987	In the unlikely case that you want to destroy the perl interpreter, here
988	is the corresponding function.
989		1124
990	=item PerlInterpreter *staticperl	1125	=item PerlInterpreter *staticperl
991		1126
992	The perl interpreter pointer used by staticperl. Not normally so useful,	1127	The perl interpreter pointer used by staticperl. Not normally so useful,
993	but there it is.	1128	but there it is.
…		…
1006		1141
1007	=back	1142	=back
1008		1143
1009	=head1 RUNTIME FUNCTIONALITY	1144	=head1 RUNTIME FUNCTIONALITY
1010		1145
1011	Binaries created with C<mkbundle>/C<mkperl> contain extra functions, which	1146	Binaries created with C<mkbundle>/C<mkperl> contain extra functionality,
1012	are required to access the bundled perl sources, but might be useful for	1147	mostly related to the extra files bundled in the binary (the virtual
1013	other purposes.	1148	filesystem). All of this data is statically compiled into the binary, and
		1149	accessing means copying it from a read-only section of your binary. Data
		1150	pages in this way is usually freed by the operating system, as it isn't
		1151	use more the onace.
		1152
		1153	=head2 VIRTUAL FILESYSTEM
		1154
		1155	Every bundle has a virtual filesystem. The only information stored in it
		1156	is the path and contents of each file that was bundled.
		1157
		1158	=head3 LAYOUT
		1159
		1160	Any path starting with an ampersand (F<&>) or exclamation mark (F<!>) are
		1161	reserved by F<staticperl>. They must only be used as described in this
		1162	section.
		1163
		1164	=over 4
		1165
		1166	=item !
		1167
		1168	All files that typically cannot be loaded from memory (such as dynamic
		1169	objects or shared libraries), but have to reside in the filesystem, are
		1170	prefixed with F<!>. Typically these files get written out to some
		1171	(semi-)temporary directory shortly after program startup, or before being
		1172	used.
		1173
		1174	=item !boot
		1175
		1176	The bootstrap file, if specified during bundling.
		1177
		1178	=item !auto/
		1179
		1180	Shared objects or dlls corresponding to dynamically-linked perl extensions
		1181	are stored with an F<!auto/> prefix.
		1182
		1183	=item !lib/
		1184
		1185	External shared libraries are stored in this directory.
		1186
		1187	=item any letter
		1188
		1189	Any path starting with a letter is a perl library file. For example,
		1190	F<Coro/AIO.pm> corresponds to the file loaded by C<use Coro::AIO>, and
		1191	F<Coro/jit.pl> corresponds to C<require "Coro/jit.pl">.
		1192
		1193	Obviously, module names shouldn't start with any other characters than
		1194	letters :)
		1195
		1196	=back
		1197
		1198	=head3 FUNCTIONS
		1199
		1200	=over 4
		1201
		1202	=item $file = staticperl::find $path
		1203
		1204	Returns the data associated with the given C<$path>
		1205	(e.g. C<Digest/MD5.pm>, C<auto/POSIX/autosplit.ix>).
		1206
		1207	Returns C<undef> if the file isn't embedded.
		1208
		1209	=item @paths = staticperl::list
		1210
		1211	Returns the list of all paths embedded in this binary.
		1212
		1213	=back
		1214
		1215	=head2 EXTRA FEATURES
1014		1216
1015	In addition, for the embedded loading of perl files to work, F<staticperl>	1217	In addition, for the embedded loading of perl files to work, F<staticperl>
1016	overrides the C<@INC> array.	1218	overrides the C<@INC> array.
1017		1219
1018	=over 4
1019
1020	=item $file = staticperl::find $path
1021
1022	Returns the data associated with the given C<$path>
1023	(e.g. C<Digest/MD5.pm>, C<auto/POSIX/autosplit.ix>), which is basically
1024	the UNIX path relative to the perl library directory.
1025
1026	Returns C<undef> if the file isn't embedded.
1027
1028	=item @paths = staticperl::list
1029
1030	Returns the list of all paths embedded in this binary.
1031
1032	=back
1033
1034	=head1 FULLY STATIC BINARIES - BUILDROOT	1220	=head1 FULLY STATIC BINARIES - UCLIBC AND BUILDROOT
1035		1221
1036	To make truly static (Linux-) libraries, you might want to have a look at	1222	To make truly static (Linux-) libraries, you might want to have a look at
1037	buildroot (L<http://buildroot.uclibc.org/>).	1223	buildroot (L<http://buildroot.uclibc.org/>).
1038		1224
1039	Buildroot is primarily meant to set up a cross-compile environment (which	1225	Buildroot is primarily meant to set up a cross-compile environment (which
…		…
1046	good experiences with GCC 4.4.x but not GCC 4.5.	1232	good experiences with GCC 4.4.x but not GCC 4.5.
1047		1233
1048	To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections	1234	To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections
1049	-finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386>	1235	-finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386>
1050	doesn't decrease codesize much, but it makes the file much more	1236	doesn't decrease codesize much, but it makes the file much more
1051	compressible.	1237	compressible (and the execution a lot slower...).
1052		1238
1053	If you don't need Coro or threads, you can go with "linuxthreads.old" (or	1239	If you don't need Coro or threads, you can go with "linuxthreads.old" (or
1054	no thread support). For Coro, it is highly recommended to switch to a	1240	no thread support). For Coro, it is highly recommended to switch to a
1055	uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201	1241	uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201
1056	snapshot) and enable NPTL, otherwise Coro needs to be configured with the	1242	snapshot) and enable NPTL, otherwise Coro needs to be configured with the
…		…
1058	twice the address space needed for stacks).	1244	twice the address space needed for stacks).
1059		1245
1060	If you use C<linuxthreads.old>, then you should also be aware that	1246	If you use C<linuxthreads.old>, then you should also be aware that
1061	uClibc shares C<errno> between all threads when statically linking. See	1247	uClibc shares C<errno> between all threads when statically linking. See
1062	L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a	1248	L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a
1063	workaround (And L<https://bugs.uclibc.org/2089> for discussion).	1249	workaround (and L<https://bugs.uclibc.org/2089> for discussion).
1064		1250
1065	C<ccache> support is also recommended, especially if you want	1251	C<ccache> support is also recommended, especially if you want
1066	to play around with buildroot options. Enabling the C<miniperl>	1252	to play around with buildroot options. Enabling the C<miniperl>
1067	package will probably enable all options required for a successful	1253	package will probably enable all options required for a successful
1068	perl build. F<staticperl> itself additionally needs either C<wget>	1254	perl build. F<staticperl> itself additionally needs either C<wget>
…		…
1076	it from working properly in a chroot - either use dash (and link it to	1262	it from working properly in a chroot - either use dash (and link it to
1077	F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's	1263	F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's
1078	built-in ash shell.	1264	built-in ash shell.
1079		1265
1080	Finally, you need F</dev/null> inside the chroot for many scripts to work	1266	Finally, you need F</dev/null> inside the chroot for many scripts to work
1081	- F<cp /dev/null output/target/dev> or bind-mounting your F</dev> will	1267	- either F<cp /dev/null output/target/dev> or bind-mounting your F</dev>
1082	both provide this.	1268	will provide this.
1083		1269
1084	After you have compiled and set up your buildroot target, you can copy	1270	After you have compiled and set up your buildroot target, you can copy
1085	F<staticperl> from the C<App::Staticperl> distribution or from your	1271	F<staticperl> from the C<App::Staticperl> distribution or from your
1086	perl f<bin> directory (if you installed it) into the F<output/target>	1272	perl F<bin> directory (if you installed it) into the F<output/target>
1087	filesystem, chroot inside and run it.	1273	filesystem, chroot inside and run it.
1088		1274
1089	=head1 RECIPES / SPECIFIC MODULES	1275	=head1 RECIPES / SPECIFIC MODULES
1090		1276
1091	This section contains some common(?) recipes and information about	1277	This section contains some common(?) recipes and information about
…		…
1100		1286
1101	Some functionality in the utf8 module, such as swash handling (used	1287	Some functionality in the utf8 module, such as swash handling (used
1102	for unicode character ranges in regexes) is implemented in the	1288	for unicode character ranges in regexes) is implemented in the
1103	C<"utf8_heavy.pl"> library:	1289	C<"utf8_heavy.pl"> library:
1104		1290
1105	-M'"utf8_heavy.pl"'	1291	-Mutf8_heavy.pl
1106		1292
1107	Many Unicode properties in turn are defined in separate modules,	1293	Many Unicode properties in turn are defined in separate modules,
1108	such as C<"unicore/Heavy.pl"> and more specific data tables such as	1294	such as C<"unicore/Heavy.pl"> and more specific data tables such as
1109	C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables	1295	C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables
1110	are big (7MB uncompressed, although F<staticperl> contains special	1296	are big (7MB uncompressed, although F<staticperl> contains special
1111	handling for those files), so including them on demand by your application	1297	handling for those files), so including them on demand by your application
1112	only might pay off.	1298	only might pay off.
1113		1299
1114	To simply include the whole unicode database, use:	1300	To simply include the whole unicode database, use:
1115		1301
1116	--incglob '/unicore/*.pl'	1302	--incglob '/unicore/**.pl'
1117		1303
1118	=item AnyEvent	1304	=item AnyEvent
1119		1305
1120	AnyEvent needs a backend implementation that it will load in a delayed	1306	AnyEvent needs a backend implementation that it will load in a delayed
1121	fashion. The L<AnyEvent::Impl::Perl> backend is the default choice	1307	fashion. The L<AnyEvent::Impl::Perl> backend is the default choice
…		…
1126		1312
1127	If you want to handle IRIs or IDNs (L<AnyEvent::Util> punycode and idn	1313	If you want to handle IRIs or IDNs (L<AnyEvent::Util> punycode and idn
1128	functions), you also need to include C<"AnyEvent/Util/idna.pl"> and	1314	functions), you also need to include C<"AnyEvent/Util/idna.pl"> and
1129	C<"AnyEvent/Util/uts46data.pl">.	1315	C<"AnyEvent/Util/uts46data.pl">.
1130		1316
1131	Or you can use C<--usepacklist> and specify C<-MAnyEvent> to include	1317	Or you can use C<--usepacklists> and specify C<-MAnyEvent> to include
1132	everything.	1318	everything.
		1319
		1320	=item Cairo
		1321
		1322	See Glib, same problem, same solution.
1133		1323
1134	=item Carp	1324	=item Carp
1135		1325
1136	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of	1326	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of
1137	perl 5.12.2 (maybe earlier), this dependency no longer exists.	1327	perl 5.12.2 (maybe earlier), this dependency no longer exists.
…		…
1140		1330
1141	The F<perl -V> switch (as well as many modules) needs L<Config>, which in	1331	The F<perl -V> switch (as well as many modules) needs L<Config>, which in
1142	turn might need L<"Config_heavy.pl">. Including the latter gives you	1332	turn might need L<"Config_heavy.pl">. Including the latter gives you
1143	both.	1333	both.
1144		1334
		1335	=item Glib
		1336
		1337	Glib literally requires Glib to be installed already to build - it tries
		1338	to fake this by running Glib out of the build directory before being
		1339	built. F<staticperl> tries to work around this by forcing C<MAN1PODS> and
		1340	C<MAN3PODS> to be empty via the C<PERL_MM_OPT> environment variable.
		1341
		1342	=item Gtk2
		1343
		1344	See Pango, same problems, same solution.
		1345
		1346	=item Pango
		1347
		1348	In addition to the C<MAN3PODS> problem in Glib, Pango also routes around
		1349	L<ExtUtils::MakeMaker> by compiling its files on its own. F<staticperl>
		1350	tries to patch L<ExtUtils::MM_Unix> to route around Pango.
		1351
1145	=item Term::ReadLine::Perl	1352	=item Term::ReadLine::Perl
1146		1353
1147	Also needs L<Term::ReadLine::readline>, or C<--usepacklist>.	1354	Also needs L<Term::ReadLine::readline>, or C<--usepacklists>.
1148		1355
1149	=item URI	1356	=item URI
1150		1357
1151	URI implements schemes as separate modules - the generic URL scheme is	1358	URI implements schemes as separate modules - the generic URL scheme is
1152	implemented in L<URI::_generic>, HTTP is implemented in L<URI::http>. If	1359	implemented in L<URI::_generic>, HTTP is implemented in L<URI::http>. If
1153	you need to use any of these schemes, you should include these manually,	1360	you need to use any of these schemes, you should include these manually,
1154	or use C<--usepacklist>.	1361	or use C<--usepacklists>.
1155		1362
1156	=back	1363	=back
1157		1364
1158	=head2 RECIPES	1365	=head2 RECIPES
1159		1366
1160	=over 4	1367	=over 4
1161		1368
1162	=item Linking everything in	1369	=item Just link everything in
1163		1370
1164	To link just about everything installed in the perl library into a new	1371	To link just about everything installed in the perl library into a new
1165	perl, try this:	1372	perl, try this (the first time this runs it will take a long time, as a
		1373	lot of files need to be parsed):
1166		1374
1167	staticperl mkperl --strip ppi --incglob '*'	1375	staticperl mkperl -v --strip ppi --incglob '*'
1168		1376
		1377	If you don't mind the extra megabytes, this can be a very effective way of
		1378	creating bundles without having to worry about forgetting any modules.
		1379
		1380	You get even more useful variants of this method by first selecting
		1381	everything, and then excluding stuff you are reasonable sure not to need -
		1382	L<bigperl\|http://staticperl.schmorp.de/bigperl.html> uses this approach.
		1383
1169	=item Getting rid of netdb function	1384	=item Getting rid of netdb functions
1170		1385
1171	The perl core has lots of netdb functions (C<getnetbyname>, C<getgrent>	1386	The perl core has lots of netdb functions (C<getnetbyname>, C<getgrent>
1172	and so on) that few applications use. You can avoid compiling them in by	1387	and so on) that few applications use. You can avoid compiling them in by
1173	putting the following fragment into a C<preconfigure> hook:	1388	putting the following fragment into a C<preconfigure> hook:
1174		1389
…		…
1191	do	1406	do
1192	PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"	1407	PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"
1193	done	1408	done
1194	}	1409	}
1195		1410
1196	This mostly gains space when linking staticaly, as the functions will	1411	This mostly gains space when linking statically, as the functions will
1197	likely not be linked in. The gain for dynamically-linked binaries is	1412	likely not be linked in. The gain for dynamically-linked binaries is
1198	smaller.	1413	smaller.
1199		1414
1200	Also, this leaves C<gethostbyname> in - not only is it actually used	1415	Also, this leaves C<gethostbyname> in - not only is it actually used
1201	often, the L<Socket> module also exposes it, so leaving it out usually	1416	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.27 by root, Tue Dec 21 19:32:34 2010 UTC vs. Revision 1.48 by root, Sun Jul 10 01:37:56 2011 UTC

Diff Legend

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.27 by root, Tue Dec 21 19:32:34 2010 UTC vs.
Revision 1.48 by root, Sun Jul 10 01:37:56 2011 UTC