Man page for betatar
NAME
betatar - BETA tar(1) front-end
SYNOPSIS
betatar [--help] [--extent] [--domain] [--full] [--exclude
string ] [--ast] [--asm] [--code] [--debug] [--job] [--dump]
[--verbose] [--noCompress] [--gzip] [--list] file...
AVAILABILITY
The Mjolner BETA tar(1) front-end is available as part of
the Mjolner BETA System from Mjolner Informatics.
DESCRIPTION
betatar is an front-end to the tar(1) file archive system on
UNIX systems. betatar is used to create a tar(1) 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 pro-
gram in order to move this program to another installation
for further work (debugging or further development). Typi-
cal usages include moving a program between, say, a Linux PC
at home and the UNIX workstation at work, between different
development teams.
betatar offers many different options for controlling which
files are packaged into the tar file. The most important
aspect of betatar is that it ensures that all necessary
files are collected into the tar(1) 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 tar(1) file, depending on the different options speci-
fied to betatar.
OPTIONS
--help
Print this help info
--extent
Traverse the entire dependency graph, including BODY
and MDBODY fragments.
--domain
Traverse the dependency graph, ignoring BODY and MDBODY
fragments.
--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 tar(1)
file).
--exclude string
Ignore fragments found in the traversal if they contain
string in their filename, surrounded by '/' (e.g. --
exclude basiclib will result in all fragments contain-
ing '/basiclib/' will be ignored. Note: string may be
any egrep(1) pattern.
This option may be specified repeatedly in the command
line, with different strings. The effect will be, that
all these fragments are ignored.
--ast
Include .ast/.astL files in the tar(1) file (if the
corresponding .bet file are selected).
--asm
Include ..s assembler files (if present) in the tar(1)
file (if the corresponding .bet file are selected).
--code
Include .o code files (if present) in the tar file (if
the corresponding .bet file are selected).
--debug
Include ..db debug files (if present) in the tar file
(if the corresponding .bet file are selected).
--job
Include the .job file (if present)
--dump
Include the .dump file (if present)
--verbose
print what is saved onto the tar file
--noCompress
do not compress the tar file
--gzip
use gzip(1) instead of compress(1) to compress the tar
file.
--list
list the files to be packed. Do not actually pack the
files.
ENVIRONMENT
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 BETA System.
SEE ALSO
beta(1) - BETA Compiler
valhalla(1) - BETA Source-Level Debugger
betawc(1) - BETA fragment analyser
betafs(1) - Mjolner BETA Fragment Structure Lister
sif(1) - Hyper-Structure Editor
BUGS
Currently, betatar packs the files with full file path
specifications, making it difficult to unpack the files at
another location.
AUTHORS
The BETA tar(1) front-end is developed by Mjolner Informat-
ics as part of the Mjolner BETA System.
Questions, bug-reports, etc. may be directed to
support@mjolner.dk if the local support organization cannot
find solutions to the problems.
For more information of the Mjolner BETA System, please con-
tact Mjolner Informatics, Science Park Aarhus, Gustav Wieds
Vej 10, DK-8000 Aarhus C, Denmark, phone: +45 86 20 20 00,
fax: +45 86 20 12 22, e-mail: info@mjolner.dk.