import repository from arizona
[raven.git] / webpage / tutpkg.html
1 <html>
2 <head>
3 <title> Stork Project </title>
4 <LINK href="stork.css" rel="stylesheet" type="text/css">
5
6 </head>
7
8 <body>
9
10
11 <div class="display" align="center">
12         <table border="0">
13         <tr>
14                 <td width="170" valign="top">
15
16                                 <br/>
17                                 <table cellpadding="3" width="170" id="links" class="links">
18                                         <tr>
19                                                 <td align="right">
20
21                                                         <ul class="links">
22
23                                                                 <a href = "index.html"><h3>Stork</h3></a>
24                                                                 <li class="links"><a href="tutmain.html">Stork Tutorial</a></li>
25
26                                                                 <li class="links"><a href="advanced.html">Advanced Usage</a></li>
27                                                                 <li class="links"><a href="arch.html">Stork Architecture</a></li>
28                                                                 <li class="links"><a href="filelist.html">Stork File List</a></li>
29                                                                 <li class="links"><a href="about.html">About Us</a></li>
30                                                                 <li class="links"><a href="apps.html">Related Links</a></li>
31                                                                 <li class="links"><a href="contact.html">Contact Stork</a></li>
32                                                                 <h4>Links</h4>
33                                                                 <li class="links"><a href="http://appmanager.berkeley.intel-research.net/plcontrol/apps.php?appid=1029">
34                                                                 Slice Status</a></li>
35                                                                 <li class="links"><a href="https://stork-repository.cs.arizona.edu">Stork Repository</a></li>
36                                                         </ul>
37
38                                                  </td>
39                                         </tr>
40                                 </table>
41                                 <br/>
42                 </td>
43
44                 <td valign="top">
45                 <table class="info" cellpadding="0" width="700" >
46                 <tr  height="75"><td colspan="3"><img style="margin-left: -0px;" src="images/stork-header.png" alt="stork logo"/></td></tr>
47                 <tr  bgcolor="#444444" class="headerrow" width="100%" height="2">
48
49                         <th colspan="2"> Stork Tutorial </th>
50
51                 </tr>
52                 <tr valign="top" align="left">
53
54                         <td>
55                                 <table cellpadding="8" id="content" class="content">
56                                         <tr>
57                                                 <td>
58
59                                                         <h1><a name = "top"></a>Stork Tutorial: Packages</h1>
60
61                                                         <a name = "tarball"><h3>Creating a Package</h3></a>
62                                                         <p>Stork currently supports two types of packages: RPMs and tarballs.
63                                                         Stork will install RPM packages according to the package scripts. RPMs
64                                                         are generally suggested for complex installations, or where the package needs
65                                                         to be installed outside of /root. However, for simple packages, it can be more
66                                                         efficient to use a simple tarball package.
67
68                                                         <p>Creating a tarball package can be a great way to distribute your own
69                                                         applications. With Stork, you can easily distribute your software to every
70                                                         node that needs it. Stork also allows you to execute scripts before and
71                                                         after you install or uninstall, making tarballs even more powerful.
72                                                         Including scripts in your tarball is very simple. Just package
73                                                         '.preinstall', '.postinstall', '.preremove', and/or '.postremove' scripts
74                                                         along with your own files. Stork will automatically execute the script when
75                                                         the user decides to install or uninstall your package. The scripts will run
76                                                         from the same directory the tarball is unpacked (typically '/root/' or what
77                                                         ever is defined to be the home directory). Note that these scripts are
78                                                         completely optional.
79                                                         <p>For example, consider a simple directory called <i>directory</i> full
80                                                         of dummy files, and also four scripts, <i>.preinstall,
81                                                         .postinstall, .preremove, .postremove</i>. We can create a
82                                                         simple zipped tarball by running the command:
83
84                                                         <br><code><b>  tar -czf <i>mypackage.tar.gz</i> directory ... </b></code>
85
86                                                         <br>Where "mypackage" is the name of the tarball to be created, and the
87                                                         directory is the directory we wish to make into a package. Instead
88                                                         directories, files can also be used.
89                                                         <p>Upon installing this package with
90                                                         Stork, Stork will automatically run .preinstall, and will run
91                                                         .postinstall after installation. This allows the package creator to
92                                                         include scripts to confirm that installation is going to occur, and confirm
93                                                         that it worked. Likewise, when the package is uninstalled, the preremove and
94                                                         postremove scripts work in the same way.
95                                                                                                                 <p><img src="blkfade.gif" width="100%"></img>
96
97                                                         <p>After you have created a package, you can
98                                                         <a href="tutinst.html">install Stork, if you haven't already</a>. If so,
99                                                         move on to <a href="tutgen.html">creating an identity</a>.
100
101                                                         <p>Return to the <a href="tutmain.html">tutorial contents.</a>
102
103
104                                                         <center><a href = "index.html">Home</a>     <a href = "#top">Top</a></center>
105
106
107                                                 </td>
108                                         </tr>
109                                 </table>
110                         </td>
111                 </tr>
112
113        </table>
114        </td>
115
116      </tr>
117      <tr>
118         <td></td>
119         <td>
120                 <a href="http://www.planet-lab.org"><img style="border: 0px; border-style: none;" src="images/powered_by_pl_grey.png" alt="powered by planetlab"></a>
121
122                                         <a href="http://www.cs.arizona.edu"><img style="position:relative; left: 20px; border: 0px; border-style: none;" src="images/template_logo_small_grey.png" alt="University of Arizona, Computer Science logo"></a>
123
124         </td>
125      </tr>
126
127 </table>
128
129 </div>
130
131
132 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
133 </script>
134 <script type="text/javascript">
135 _uacct = "UA-1868232-1";
136 urchinTracker();
137 </script>
138 </body>
139 </html>