• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..07-May-2022-

announce/H03-May-2022-13,2498,713

css/H03-May-2022-454389

img/H03-May-2022-

js/H03-May-2022-

READMEH A D01-Jun-20196.5 KiB201133

corefunctions.phpH A D01-Jun-20195.8 KiB163111

credits.phpH A D01-Jun-20194.3 KiB6350

development.phpH A D01-Jun-20192.2 KiB6149

documentation.php.inH A D01-Jun-20192.9 KiB6555

downloads.phpH A D01-Jun-20192.3 KiB5848

examples.phpH A D01-Jun-20199 KiB263231

index.phpH A D01-Jun-20195.9 KiB122103

simplepie.incH A D01-Jun-2019436.3 KiB17,76916,413

template.phpH A D01-Jun-2019563 3419

README

12007-03-31: Since the conversion to subversion these instructions are even
2more dated, but we keep them for a historical reference.  Instead, follow the
3directions in ../README.Release_Manager_Cookbook.
4
511-27-06: This may work, but it is deprecated. Please follow the
6instructions contained in README.Release_Manager_Cookbook.
7
8
9Remote installation of the PLplot web site
10==========================================
11
12We are heading towards a fully automated, remote web site management for
13the PLplot project.  For now there are five areas in the site that should
14be treated individually.  Note that the instructions below are valid for
15the present situation, as in 2004-02, in which the web site is hosted by
16SourceForge.  This document must be updated in the enventuality of a moving
17to another host.
18
19The uploading of the five areas as described below are non-interfering, in
20the sense that each one can be done without affecting the others.
21
22
23Main www area
24-------------
25
26The sources for this area are in the CVS module www.  You must be a
27developer in the PLplot project at SourceForge in order to checkout, modify
28and upload the web site.
29
30To obtain a fresh CVS tree:
31
32    export CVS_RSH=ssh
33    cvs -d :ext:joeplplotter@cvs.sf.net/cvsroot/plplot co www
34
35To install the whole web site, just type:
36
37    cd www
38    WWW_USER=joeplplotter make
39
40and everything will be built and uploaded automatically, including the
41stuff in the announce directory.  Sensible variables are defined in file
42Makefile-vars, which is included by both Makefile and announce/Makefile.
43
44Needless to say, this only works with GNU make.  It is better to run make
45under ssh-agent/ssh-add, otherwise you will be prompted several times for
46your SF password.
47
48Caveat: the command above will happily upload the entire contents of the
49subdirectories.  This means that it may upload useless files, most notably
50the CVS directories present when working from a cvs checked out source.
51Using cvs export is more appropriate here, although the useless files will
52not hurt the web site.  I may try to find a fix for this in the future.
53
54It is also possible to install individual files by overriding the FILES
55variable in the Makefile, like this:
56
57    make install FILES="resources/index.html examples/index.html"
58
59
60Examples area
61-------------
62
63The examples area in the web site need a set of PNG files as well as the
64demos source files that are obtained from the PLplot source tree.  To
65obtain it from CVS, do:
66
67    export CVS_RSH=ssh
68    cvs -d :ext:joeplplotter@cvs.sf.net/cvsroot/plplot co plplot
69
70Then go to the plplot directory and type:
71
72    WWW_USER=joeplplotter scripts/htdocs-gen_plot-examples.sh
73
74This will build the PNG files and upload everything to the
75htdocs/examples-data directory in the SF shell server.
76
77To avoid rebuild of the whole project, launch it like this:
78
79    build=false scripts/htdocs-gen_plot-examples.sh
80
81
82DocBook area
83------------
84
85The documentation files (HTML, PDF, info, etc) generated from the DocBook
86sources are uploaded to the htdocs/docbook-manual directory in
87shell.sf.net.  They are automatically generated at the PLplot source tree
88by doing:
89
90    ./configure --enable-builddoc
91    cd doc/docbook/src
92    make
93
94Note that you will need several tools for processing the DocBook sources.
95See doc/docbook/README.developers for details.
96
97To install the DocBook area in the web site, do:
98
99    make WWW_USER=joeplplotter www-install
100
101
102CVS snapshot tarballs area
103--------------------------
104
105To generate a cvs snapshot tarball, use the make-cvs-tarball.sh in the
106directory scripts.  This script accepts many arguments, like the login anme
107in teh remote system, the branch name, and a version string.  Type:
108
109    make-cvs-tarbal.sh -h
110
111For a usage notice.
112
113A typical usage would be:
114
115    make-cvs-tarball.sh -v 5.3.0.cvs -r v5_3_0 -u joeplplotter
116
117The -r option is the CVS branch label from which the tarball is built. It
118default to HEAD.  The -v argument is the version string that will be
119substituted in the argument of the AC_INIT macro call in configure.ac.  If
120it is absent, then it will be automatically generated from the current
121date, like 5.3.0.cvs.20040207.
122
123You can prevent the building of the Docbook documentation (and, by
124consequence, its inclusion in the tarball), by giving the option -n to
125make-cvs-tarbal.sh.
126
127The resulting tarball can be uploaded to htdocs/cvs-tarball in the web site
128with the upload-cvs-tarball.sh, like this:
129
130    WWW_USER=joeplplotter upload-cvs-tarball.sh plplot-5.3.0.cvs.20040207.tar.gz
131
132A file called <tarball>.asc containing the detached GPG signature will also
133be generated and uploaded.  To override the default GPG key, use the
134environment variable GPGKEY, like this:
135
136    GPGKEY=0x1234ABCD upload-cvs-tarball.sh tarball.tar.gz
137
138
139The release process
140-------------------
141
142Tarball releases are generated with the make-cvs-tarball.sh script as
143described above.  The script tags the CVS repository with a unique tag
144generated from the current date and time.  This tag has the following
145structure:
146
147    cvs-tarball_<year>-<month>-<day>-<hour>-<minutes>-<seconds>
148
149where the time is UTC-based.
150
151This tag can be used later to tag the final release with a symbolic string
152(vM_N_P) in the CVS repository. Here is the algorithm for a typical release
153cycle (for the sake of the example, let us say we are going to release
154version 5.6.7):
155
1560) Change the release number in AC_INIT to 5.6.7 in configure.ac
157
1581) Generate the tarball with a command like:
159   path/to/make-cvs-tarball.sh -v 5.6.7 2>&1 | tee build.log
160
1612) Test the generated tarball (plplot-5.6.7.tar.gz)
162   You might also give options -c an -i to make some checks automatic
163
1643) Are you happy with the tarball?
165   NO:
166     Make changes in CVS and go back to 1)
167   YES:
168     4) Release the tarball
169     5) Tag the cvs repository with:
170        cvs rtag -r cvs-tarball-<date>-<time> v5_6_7
171        (where cvs-tarball-<date>-<time> was obtained in step 1)
172
1736) Remove the temporary tags using scripts/rm-cvs-tarball-tags.pl
174
175Option -r of make-cvs-tarball.sh must be used if the release is being taken
176from a branch in the CVS repository.
177
178
179Debian area
180-----------
181
182This area is maintained by the Debian maintainer of the PLplot packages.
183To generate the Debian package, install the devscripts packages, go to the
184top_scrdir directory and type:
185
186    debuild -us -uc -i
187
188Go then to the upper directory and launch the uplaod-debs.pl script:
189
190    cd ..
191    WWW_USER=joeplplotter plplot/debian/upload-debs.pl
192
193The packages, as well as an automatically generated index.html will be
194uploaded to htdocs/debian.
195
196 -- Rafael Laboissiere <rlaboiss@users.sf.net>
197
198Local Variables:
199mode: indented-text
200End:
201