-
Notifications
You must be signed in to change notification settings - Fork 2
/
tartos.html
133 lines (113 loc) · 3.42 KB
/
tartos.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Man page of tartos</TITLE>
</HEAD><BODY>
<H1>tartos</H1>
Section: User Commands (1)<BR>Updated: Apr 041, 2015<BR><A HREF="#index">Index</A>
<A HREF="/cgi-bin/man/man2html">Return to Main Contents</A><HR>
<P>
<A NAME="lbAB"> </A>
<H2>NAME</H2>
tartos - TAR to shell script
<A NAME="lbAC"> </A>
<H2>SYNOPSIS</H2>
<B>tartos</B>
[ -<B>o</B> outfile ]
[ -<B>O</B> outfile ]
<A NAME="lbAD"> </A>
<H2>DESCRIPTION</H2>
<B>tartos</B>
<P>
The tartos script is a standalone bash shell script which binds different type of TAR archives
to a single shell script (bash). This kind of approach is generally adopted to make a single
install script from an existing tar archives with executable or installable software. It can
be used to make a self extracting archive/installer which does some additional jobs like
installing softwares, compared to the conventional tar archive files. The tartos script itself
is written in bash and thus depends on it and on the package tar.
<P>
<A NAME="lbAE"> </A>
<H2>OPTIONS</H2>
The command line options are:
<DL COMPACT>
<DT><B>-o outfile</B>
<DD>
Output directory where the script will install archive later
<DT><B>-O outfile</B>
<DD>
Output directory where the script will install archive later
<DT><B>-h</B>
<DD>
show help menu
<DT><B>--help</B>
<DD>
show help menu
</DL>
<A NAME="lbAF"> </A>
<H2>EXAMPLES</H2>
<B>tartos</B>
<P>
tartos archive script "command"
<P>
tartos archive script "command" -o directory
<P>
tartos -O directory archive script "command"
<P>
<A NAME="lbAG"> </A>
<H2>ADVANCED USE</H2>
<B>tartos</B>
<P>
tartos archive scriptname "commands" -o outputdir
<P>
1. It can take upto four arguments, the first argument is a tar archive,
<P>
second one is the name of the target script file
<P>
and third one is custom command and the 4th argument is of type [-o outdir]
<P>
[-o outdir] can take any position as long as the sequence of the first three argument is maintained.
<P>
Ex1: tartos path_to_tar_file script_name_or_path command
<P>
Ex2: tartos archive script command -o directory
<P>
Ex3: tartos -O directory archive script command
<P>
-o and -O is equivalent
<P>
2. It will ask for necessary arguments/info as it needs on the way.
<P>
3. Give commands inside quotation mark: double quotation is recommended
<P>
4. Best way of giving custom command is to write them in another script and put that script
<P>
as a command into tartos command input.
<P>
Ex: Enter custom command or script (if any): ./mycustomscript
<P>
if the path to the script contains space, use double quotes
<P>
<A NAME="lbAH"> </A>
<H2>BUGS</H2>
Report bugs to <<A HREF="http://github.com/neurobin/tartos">http://github.com/neurobin/tartos</A>>
<A NAME="lbAI"> </A>
<H2>AUTHOR</H2>
Jahidul Hamid
<<A HREF="http://github.com/neurobin">http://github.com/neurobin</A>>
<HR>
<A NAME="index"> </A><H2>Index</H2>
<DL>
<DT><A HREF="#lbAB">NAME</A><DD>
<DT><A HREF="#lbAC">SYNOPSIS</A><DD>
<DT><A HREF="#lbAD">DESCRIPTION</A><DD>
<DT><A HREF="#lbAE">OPTIONS</A><DD>
<DT><A HREF="#lbAF">EXAMPLES</A><DD>
<DT><A HREF="#lbAG">ADVANCED USE</A><DD>
<DT><A HREF="#lbAH">BUGS</A><DD>
<DT><A HREF="#lbAI">AUTHOR</A><DD>
</DL>
<HR>
This document was created by
<A HREF="/cgi-bin/man/man2html">man2html</A>,
using the manual pages.<BR>
Time: 09:04:49 GMT, April 04, 2015
</BODY>
</HTML>