betatar - BETA archiving program
betatar [--help|-h] [--extent|-e] [--domain|-d] [--full|-f]
[--ast|-a] [--asm|-s] [--code|-c] [--debug|-b] [--job|-j]
[--dump|-u] [--total|-t] [--ignore|-x rexps ] [--include|-i
rexps ] [--verbose|-v] [--compress|-m] [--gzip|-g]
[--zip|-z] [--list|-l] file...
The Mjolner System betatar(1) utility is available as part
of the Mjolner System from Mjolner Informatics.
betatar is an archiving program. betatar(1) makes use dif-
ferent external programs, such as tar(1) or zip(1) and for
compressing the files, betatar(1) makes use of compress(1)
or gzip(1) Which is actually used depends on the options
(see later).
betatar is used to create an archive of all files related to
a BETA fragment file (BETA source files, etc.) betatar is
intended to be used for packaging the entire set of files,
contributing to a given BETA program in order to move this
program to another installation for further work (debugging
or further development). Typical usages include moving a
program between, say, a PC at home and the UNIX workstation
at work, or between different development teams.
betatar offers many different options for controlling which
files are packaged into the archive file. The most impor-
tant aspect of betatar is that it ensures that all necessary
files are collected into the archive file (except if certain
options are used - see later), such that, when unpacked, all
needed files will be in place for continued work.
betatar works by traversing the dependency graph of the
fragment graph, following ORIGIN, INCLUDE, BODY and MDBODY
fragment links, starting at the fragment specified in the
file given as argument to betatar. During this traversal
(identical to the dependency analysis conducted by the BETA
compiler), betatar selects the fragments to be included in
the archive file, depending on the different options speci-
fied to betatar.
-h
--help
Print this help info
-e
--extent
Traverse the entire dependency graph, including BODY
and MDBODY fragments.
-d
--domain
Traverse the dependency graph, ignoring BODY and MDBODY
fragments.
-f
--full
Choose all fragments found during the traversal of the
dependency graph. This includes standard libraries
from the Mjolner BETA System. If --full is not speci-
fied, all fragments located in $BETALIB/ are ignored
(i.e. standard files are not packed into the archive
file).
-a
--ast
Include .ast/.astL files in the archive file (if the
corresponding .bet file are selected).
-s
--asm
Include ..s assembler files (if present) in the archive
file (if the corresponding .bet file are selected).
-c
--code
Include .o code files (if present) in the archive file
(if the corresponding .bet file are selected).
-b
--debug
Include ..db debug files (if present) in the archive
file (if the corresponding .bet file are selected).
-j
--job
Include the .job file (if present)
-u
--dump
Include the .dump file (if present)
-t
--total
Include all file types (equiv. to "--ast --asm --code
--debup --job --dump")
-x
--ignore string
Ignore fragments found in the traversal if they contain
rexps in their filename (e.g. --ignore basiclib will
result in all fragments containing 'basiclib' will be
ignored. Note: rexps may be any regexp pattern.
This option may have more than one "rexp" in the com-
mand line, with different regexps. The effect will be,
that all these fragments are ignored. "--ignore rexp"
has precedence over all above options.
-i
--include string
Include fragments found in the traversal if they con-
tain rexps in their filename (e.g. --include basiclib
will result in all fragments containing 'basiclib' will
be included. Note: rexps may be any regexp pattern.
This option may have more than one "rexp" in the com-
mand line, with different regexps. The effect will be,
that all these fragments are included. "--include
rexp" has precedence over all above options.
-v
--verbose
print what is saved onto the archive file
-m
--compress
compress the archive file
-g
--gzip
use gzip(1) instead of compress(1) to compress the ar-
chive file.
-z
--zip
use zip(1) instead of tar(1) to pack the files.
-l
--list
list the files to be packed. Do not actually pack the
files.
betatar recognizes the environment variable $BETALIB. Please
note that this variable is given default value in the Bourne
Shell script $BETALIB/configuration/env.sh
BETALIB
Specifies where ~beta is located. If not set, beta is
assumed to be a username, and ~beta being the home
directory of that user. Is used by many tools in the
Mjolner System.
beta(1) - BETA Compiler
mjolner(1) - Mjolner Integrated Development Environment
betawc(1) - BETA fragment analyser
betafs(1) - Mjolner BETA Fragment Structure Lister
Currently, betatar packs the files with full file path
specifications, making it difficult to unpack the files at
another location.
The betatar(1) utility is developed by Mjolner Informatics
as part of the Mjolner System.
Questions, bug-reports, etc. may be directed to
support@mjolner.com if the local support organization cannot
find solutions to the problems.
For more information of the Mjolner System, please contact
Mjolner Informatics, Helsingforsgade 27, DK-8200 Aarhus N,
Denmark, phone: +45 70 27 43 43, fax: +45 70 27 43 44, e-
mail: info@mjolner.com, web: http://www.mjolner.com.
| Mjølner System: Man Pages | © 1990-2004 Mjølner Informatics |
[Modified: Tuesday June 29th 2004 at 13:19]
|