arx 0.0.0 → 0.0.1
raw patch · 4 files changed
+14/−14 lines, 4 filesPVP ok
version bump matches the API change (PVP)
API changes (from Hackage documentation)
Files
- README +4/−4
- arx.cabal +5/−5
- docs/blessed/arx.man +1/−1
- docs/blessed/arx.txt +4/−4
README view
@@ -15,10 +15,10 @@ The arx tool has no in-built notion of remote connections or server clusters; all automation is captured as Bourne compatible scripts that use a small number of UNIX utilities in a broadly portable way. At- present, the utilities used are sed, tr, head, and tar. The calls to- tar sometimes use -j and -z; these calls to tar may result in calls to- bzip2 and gzip. Scripts have been tested with dash and the GNU tools as- well as the sh and tools that are part of busybox.+ present, the utilities used are sed, tr, date, head, and tar. The calls+ to tar sometimes use -j and -z; these calls to tar may result in calls+ to bzip2 and gzip. Scripts have been tested with dash and the GNU tools+ as well as the sh and tools that are part of busybox. The tmpx subcommand of arx offers a variety of options for bundling code and a task to run. The shdat subcommand exposes the lower-level
arx.cabal view
@@ -1,5 +1,5 @@ name : arx-version : 0.0.0+version : 0.0.1 category : Text license : BSD3 license-file : LICENSE@@ -21,10 +21,10 @@ would like to use @ssh@ and @sudo@ to set an appropriate executation context, for example running: @ssh user\@example.com sudo sh@. .- The shell tools used are @head@, @sed@, @tr@ and @tar@. The calls to @tar@- sometimes use @-j@ and @-z@; these calls to @tar@ may result in calls to- @bzip2@ and @gzip@. Scripts have been tested with @dash@ and the GNU tools- as well as the @sh@ and tools that are part of @busybox@.+ The shell tools used are @head@, @sed@, @date@, @tr@ and @tar@. The calls to+ @tar@ sometimes use @-j@ and @-z@; these calls to @tar@ may result in calls+ to @bzip2@ and @gzip@. Scripts have been tested with @dash@ and the GNU+ tools as well as the @sh@ and tools that are part of @busybox@. . The @arx@ command line tool provides the @tmpx@ subcommand for preparing jobs to run and the @shdat@ subcommand for access to the low-level shell
docs/blessed/arx.man view
@@ -52,7 +52,7 @@ The \fIarx\fP tool has no in\-built notion of remote connections or server clusters; all automation is captured as Bourne compatible scripts that use a small number of UNIX utilities in a broadly portable way. At present, the-utilities used are \fIsed\fP, \fItr\fP, \fIhead\fP, and \fItar\fP. The calls to \fItar\fP+utilities used are \fIsed\fP, \fItr\fP, \fIdate\fP, \fIhead\fP, and \fItar\fP. The calls to \fItar\fP sometimes use \fI\-j\fP and \fI\-z\fP; these calls to \fItar\fP may result in calls to \fIbzip2\fP and \fIgzip\fP. Scripts have been tested with \fIdash\fP and the GNU tools as well as the \fIsh\fP and tools that are part of \fIbusybox\fP.
docs/blessed/arx.txt view
@@ -15,10 +15,10 @@ The arx tool has no in-built notion of remote connections or server clusters; all automation is captured as Bourne compatible scripts that use a small number of UNIX utilities in a broadly portable way. At- present, the utilities used are sed, tr, head, and tar. The calls to- tar sometimes use -j and -z; these calls to tar may result in calls to- bzip2 and gzip. Scripts have been tested with dash and the GNU tools as- well as the sh and tools that are part of busybox.+ present, the utilities used are sed, tr, date, head, and tar. The calls+ to tar sometimes use -j and -z; these calls to tar may result in calls+ to bzip2 and gzip. Scripts have been tested with dash and the GNU tools+ as well as the sh and tools that are part of busybox. The tmpx subcommand of arx offers a variety of options for bundling code and a task to run. The shdat subcommand exposes the lower-level