--- shtool.pod 2001/06/13 21:30:05 1.51
+++ shtool.pod 2001/06/14 14:24:16 1.52
@@ -29,10 +29,10 @@
=head1 SYNOPSIS
-B<shtool>
-[ I<global_options> ]
-I<command>
-[ I<command_options> ]
+B<shtool>
+[ I<global_options> ]
+I<command>
+[ I<command_options> ]
[ I<command_args> ]
=head1 DESCRIPTION
@@ -66,7 +66,7 @@
were locally adjusted because no centralized maintainance location exists, of
course. For B<autoconf> no such problem exists, because the resulting
C<configure> script is generated on-the-fly. The same applies to B<automake>
-and the various C<Makefile.in> files.
+and the various C<Makefile.in> files.
Only for B<libtool> one always has to grab the latest copy. But because it's
just two files (C<ltmain.sh> and C<ltconfig>), keeping a source trees in sync
@@ -89,7 +89,7 @@
files in the source tree are just auxiliary scripts. Sure, the actual amount
of script code even B<shtool> cannot reduce, but B<shtool> merges them
together into a single file and this way they optically totally disappear from
-the source tree.
+the source tree.
This is a pure aesthetical issue, of course. But keep in mind that hacking is
a piece of art. And a well layouted source tree is a piece of art for real
@@ -110,7 +110,7 @@
=head2 The goals in detail
To better understand the intentions behind B<shtool> and to avoid confusion,
-here are the original goals of the B<shtool> script:
+here are the original goals of the B<shtool> script:
=over 3
@@ -142,7 +142,7 @@
=item B<4. It has to be clean and fully documented>
This was achieved by reimplementing too ugly functionality from scratch and
-cleaning up old shell script code plus writing this complete manual page.
+cleaning up old shell script code plus writing this complete manual page.
=item B<5. It has to stay under a reasonable and common license>
@@ -190,7 +190,7 @@
Recreate the B<shtool> script with its own individual shtoolize(1) call.
-=back
+=back
=head1 COMMANDS
@@ -214,7 +214,7 @@
Pretty-prints a field-sperarated list as a table.
-=item B<prop>
+=item B<prop>
Display a processing indication though a running propeller.
@@ -292,7 +292,7 @@
constructs (terminal bold mode, environment details, date) and newline
control. Per default I<string> is written to I<stdout> followed by a newline
character (``C<\n>''). When option ``B<-n>'' is used this newline character is
-left out.
+left out.
The I<str> can contain special ``B<%>I<x>'' constructs which which
are expanded before the output is written if option ``B<-e>'' is
@@ -325,7 +325,7 @@
three characters, option ``B<-d>'' replaces the month name with the
corresponding digits, option ``B<-f>'' uses I<str> as the field separator
(default is a single space character) and option ``B<-o>'' specified the order
-in which the fields are printed.
+in which the fields are printed.
The default for I<spec> is ``C<dmy>'' which means an output of ``<day> <month>
<year>''. Any combination of the chars ``C<d>'', ``C<m>'' and ``C<y>'' or
@@ -347,7 +347,7 @@
This pretty-prints a I<sep>-sperarated list of I<str>ings as a table. Per
default a colon-separated list (I<sep>=":") is pretty printed as a
three-column (<cols>=3) table no longer than 79 chars (I<strip>=79) is
-generated where each column is 15 characters wide (I<width>=15).
+generated where each column is 15 characters wide (I<width>=15).
The trick of this command is that it avoids to use the unportable tr(1) and
fmt(1) commands and instead is based entirely on sh(1), awk(1) and sed(1)
@@ -412,7 +412,7 @@
command. Per default I<file> is moved to the target I<path>, but with option
``B<-c>'' I<file> is copied. The target file is created with owner/group set
to the current active uid/gid, but if this script is called as root (uid 0)
-the options ``B<-o>'' and ``B<-g>'' can be used to override this.
+the options ``B<-o>'' and ``B<-g>'' can be used to override this.
Additionally program executables is stripped with strip(1) after
installation if option ``B<-s>'' is used. Option ``B<-C>'' is like
@@ -484,7 +484,7 @@
creating the files of I<src-dir> by linking them into the corresponding
directories under I<dst-dir> via symbolic links. When I<src-dir> can be
reached via relative paths from I<dst-dir>, relative symbolic links are used,
-too.
+too.
Option ``B<-v>'' (verbose) can be used to enable some displaying of processing
information. Option ``B<-t>'' (trace) can be used to display all commands
@@ -496,7 +496,7 @@
The trick of this is that is provides such a high-level functionality with a
single command and hides all gory details.
-Example:
+Example:
# shell script
shtool mkshadow -v -a . /tmp/shadow
@@ -530,7 +530,7 @@
unpacks into a top-level directory `C<foobar-0.8.15/>'); third the files in
the tarball should be sorted to allow users to use the `C<tar tvf ->' command
in a reasonable way; fourth the owner and group of the files in the tarball
-for security reasons can be set to arbitrary names.
+for security reasons can be set to arbitrary names.
The input files are given by the file or directory arguments I<path>.
Directories are expanded before the comma-separated exclude (option B<-e>)
@@ -544,7 +544,7 @@
essential shell commands which are executed.
The trick of this command is that it combines the complex process of rolling a
-good tarball into a I<single> command.
+good tarball into a I<single> command.
Example:
@@ -601,7 +601,7 @@
options are contained. B<slo> parses these two options only and ignores the
remaining contents. The result is a trivial shell script on C<stdout> which
defines six variables containing the ``B<-L>'' and ``B<-l>'' options sorted by
-class:
+class:
``C<SLO_DIRS_OBJ>'' and ``C<SLO_LIBS_OBJ>'' contains the ``B<-L>'' and
``B<-l>'' options of static libraries, ``C<SLO_DIRS_PIC>'' and
@@ -632,7 +632,7 @@
cpp(1) code segments, internal variables and internal functions. The intention
for this comes from writing libraries in ANSI C. Here a common shared internal
header file is usually used for sharing information between the library
-source files.
+source files.
The operation is to parse special constructs in I<file>s, generate a few
things out of these constructs and insert them at position I<mark> in I<tfile>
@@ -689,14 +689,14 @@
#endif
intern int ours;
static int myone = 0815;
- intern int bar(void)
+ intern int bar(void)
{
ours += myone;
}
/* foo_quux.c */
#include "foo_p.h"
- int main(int argc, char *argv[])
+ int main(int argc, char *argv[])
{
int i;
ours = OURS_INIT
@@ -752,7 +752,7 @@
executable in $PATH or I<path> through one or more filenames (given by one or
more I<str> arguments). The result is the absolute filesystem path to the
program displayed on C<stdout> plus an exit code of 0 if it was really
-found.
+found.
The option ``B<-s>'' can be used to suppress the output which is useful to
just test whether a program exists with the help of the return code. The
|
