57 |
57 |
58 =over 4 |
58 =over 4 |
59 |
59 |
60 =item B<@l_prefix@/bin/openpkg rc> [B<-s>|B<--silent>] [B<-v>|B<--verbose>] [B<-d>|B<--debug>] [B<-k>|B<--keep>] I<package> I<command> [I<command> ...] |
60 =item B<@l_prefix@/bin/openpkg rc> [B<-s>|B<--silent>] [B<-v>|B<--verbose>] [B<-d>|B<--debug>] [B<-k>|B<--keep>] I<package> I<command> [I<command> ...] |
61 |
61 |
62 B<Run-Command Execution.> This executes one or more specified |
62 B<Runcommand Execution.> This executes one or more specified |
63 I<command>s in a particular I<package> or in all installed packages if |
63 I<command>s in a particular I<package> or in all installed packages if |
64 I<package> is "C<all>". Option B<--silent> can be used to explicitly |
64 I<package> is "C<all>". Option B<--silent> can be used to explicitly |
65 disable progress messages on C<stderr>. Option B<--verbose> can be used |
65 disable progress messages on C<stderr>. Option B<--verbose> can be used |
66 to explicitly enable progress messages on C<stderr>. By default, B<rc> |
66 to explicitly enable progress messages on C<stderr>. By default, B<rc> |
67 automatically determines whether progress messages should be displayed |
67 automatically determines whether progress messages should be displayed |
69 Option B<--keep> can be used for debugging purposes to keep the |
69 Option B<--keep> can be used for debugging purposes to keep the |
70 temporary files were generated during internal processing. |
70 temporary files were generated during internal processing. |
71 |
71 |
72 =item B<@l_prefix@/bin/openpkg rc> B<-p>|B<--print> I<package> I<command> [I<command> ...] |
72 =item B<@l_prefix@/bin/openpkg rc> B<-p>|B<--print> I<package> I<command> [I<command> ...] |
73 |
73 |
74 B<Run-Command Printing.> This is like the run-command execution (see |
74 B<Runcommand Printing.> This is like the run-command execution (see |
75 above), but instead of immediately executing all involved individual |
75 above), but instead of immediately executing all involved individual |
76 run-command scripts, they are concatenated (but with all configuration |
76 run-command scripts, they are concatenated (but with all configuration |
77 parts reduced to a single configuration part) and printed to C<stdout>. |
77 parts reduced to a single configuration part) and printed to C<stdout>. |
78 Use this for debugging or post-processing purposes. |
78 Use this for debugging or post-processing purposes. |
79 |
79 |
80 =item eval `B<@l_prefix@/bin/openpkg rc> B<-e>|B<--eval> I<package> I<command> [I<command> ...]` |
80 =item eval `B<@l_prefix@/bin/openpkg rc> B<-e>|B<--eval> I<package> I<command> [I<command> ...]` |
81 |
81 |
82 B<Run-Command Evaluation.> This is like the run-command execution |
82 B<Runcommand Evaluation.> This is like the run-command execution |
83 (see above), but the resulting exported shell environment variables |
83 (see above), but the resulting exported shell environment variables |
84 are output to a temporary file as a (Bourne-Shell or C-Shell syntax) |
84 are output to a temporary file as a (Bourne-Shell or C-Shell syntax) |
85 shell script, suitable for evaluation within the shell environment |
85 shell script, suitable for evaluation within the shell environment |
86 of the caller. A one-line script is printed to C<stdout> which then |
86 of the caller. A one-line script is printed to C<stdout> which then |
87 "sources" (and immediately removes) this temporary file. This is |
87 "sources" (and immediately removes) this temporary file. This is |