head	1.4;
access;
symbols;
locks; strict;
comment	@# @;


1.4
date	2003.09.09.07.46.03;	author ossp;	state Exp;
branches;
next	1.3;

1.3
date	2003.07.10.18.04.21;	author rse;	state Exp;
branches;
next	1.2;

1.2
date	2002.07.13.20.09.38;	author rse;	state Exp;
branches;
next	1.1;

1.1
date	2002.02.15.10.20.57;	author rse;	state Exp;
branches;
next	;


desc
@@


1.4
log
@flush pending work
@
text
@
#use wml::ossp area=pkg:tool subarea=rc

<title>OSSP rc</title>

<h1>Run-Command Processor</h1>

<h2>Abstract</h2>

OSSP rc is a generic run-command processor. Its primary function is to
assemble a temporary script from excerpts of one or more run-commmand
files which are built out of text snippets grouped into sections.
The user specifies the desired parts to use and also controls the
order of assembly. The program is not tied to a particular syntax for
neither the run-command section tags nor the contained scripts. By
default, the assembled script is executed by a specified interpreter
(usually a shell), but it can also be written into a temporary file
for evaluation inside a calling shell, or even just printed to stdout
for further processing.

<p>
Its primary purpose is to be used as a generic
run-command facility in an operating system or a sub-system like <a
href="http://www.openpkg.org/">OpenPKG</a>.

<h2>Documentation</h2>

<pkg_manpage name="rc" sect=1 path="/pkg/tool/rc/rc.pod">,
<pkg_manpage name="rc-sample" sect=5 path="/pkg/tool/rc/rc-sample.pod">.

<h2>Authors</h2>

<pkg_author name="Michael Schloh v. Bennewitz" mail="michael.schloh@@cw.com">

<h2>Status</h2>

<pkg_status
    stable="none" stable_date="none"
    unstable="0.7.1" unstable_date="07-Jul-2003"
	done=95>

<h2>Source</h2>

<pkg_files 
    cvs=$(CVS_ROOT_URL)/pkg/tool/rc/
    url=$(FTP_ROOT_URL)/pkg/tool/rc/
    directory=$(FTP_ROOT_DIR)/pkg/tool/rc/
    files="rc-*.tar.gz" 
	stable="none" unstable="0.7.1">
	
@


1.3
log
@update website for OSSP rc 0.7.1
@
text
@d10 13
a22 3
OSSP rc is a run-command processor. Its primary function is to scan
run-command script files for run-command sections and run the commands
listed in the sections. Its primary purpose is to be used as a generic
@


1.2
log
@add CVS references
@
text
@d16 5
d28 3
a30 3
    stable="none"    stable_date="none"
    unstable="none"  unstable_date="none"
	done=20>
d39 1
a39 1
	stable="none" unstable="none">
@


1.1
log
@finish the tool section
@
text
@d30 1
@