blob: 1fd086ccf5260f093bfb4e030b363aac983b34ab (
plain)
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
|
<!- Guide to the creation of source releases for Tcllib -->
<h1>Guide to the creation of source releases for Tcllib
</h1>
<hr>
<h2>Recap
</h2>
<table><tr><td valign=top>
<!-- The local source of this image is
tcllib/devel/cvs.branches.*
-->
<img src="http://sourceforge.net/dbimage.php?id=2221">
</td><td valign=top><p>
The CVS repository for Tcllib contains two main branches,
the HEAD for development, and RELEASES as the staging area for
official releases.
</p></td></tr></table>
<h2>Dependencies
</h2>
<h2>Creation of a new official release
</h2>
<p>To create a new official release of Tcllib the release manager has
to perform the steps described below:
</p>
<ol>
<li> Retrieve the sources at the current head
from the CVS repository, using a command like
<pre>
CVSROOT=:pserver:anonymous@cvs.tcllib.sourceforge.net:/cvsroot/tcllib
cvs -d${CVSROOT} co tcllib
</pre>
Vary this command according to taste as long as the overall
meaning is not changed. Compression options and the like.
<li> Tag these sources with a new branch tag for the new release of
tcllib, like
<pre>
cvs -d${CVSROOT} rtag tcllib
</pre>
<li> Commit the changes, then update the working directory.
<li> Use a tclsh to run the <b>sak</b> tool with the argument <i>gendist</i>, like
<pre>
tclsh /path/to/tcllib/sak.tcl gendist
</pre>
<li> This results in the creation of a <i>tcllib-VERSION</i> directory
in the current working directory, and of two archives, <i>.zip</i>,
and <i>.tar.gz</i>. A starkit will be created if <b>sdx</b> is present
in the PATH. If additionally a file named <b>tclkit</b> is present in
the current working directory a starpack will be created too, using
this tclkit as the runtime.
<li> Now follow the instructions in the Sourceforge site documentation
for uploading the archives generated by the last
step to
<b>ftp://upload.sourceforge.net/incoming</b>, and
follow the procedures for creating packages and
releases at Sourceforge.
</ol>
<p>At last notify the relevant persons in other communities like
Debian (See list of contacts) about the new release.
</p>
|
