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
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>How to prepare a Ghostscript release</title>
<!-- $Id$ -->
<!-- Originally: make.txt -->
<link rel="stylesheet" type="text/css" href="gs.css" title="Ghostscript Style">
</head>
<body>
<!-- [1.0 begin visible header] ============================================ -->
<!-- [1.1 begin headline] ================================================== -->
<h1>How to prepare a Ghostscript release</h1>
<!-- [1.1 end headline] ==================================================== -->
<!-- [1.2 begin table of contents] ========================================= -->
<h2>Table of contents</h2>
<blockquote><ul>
<li><a href="#Introduction">Introduction</a>
<li><a href="#Servers">Servers</a>
<ul>
<li><a href="#Development_files">Development sources and bug reports</a>
<li><a href="#Distribution">Distribution</a>
</ul>
<li><a href="#Release_numbering">Release numbering</a>
<li><a href="#Making_distributions">Making distributions</a>
<ul>
<li><a href="#Preparing_source">Preparing the source code</a>
<li><a href="#Testing">Testing</a>
<li><a href="#Changelog">Updating the Changelog</a>
<li><a href="#Making_Tarballs">Making the source distribution</a>
<li><a href="#Testing_on_Windows">Testing on Windows</a>
<li><a href="#Windows_distribution">Building the Windows distribution</a>
<li><a href="#Finishing_up">Finishing up</a>
<li><a href="#Beta_distributions">Beta distributions</a>
<li><a href="#Public_releases">Public releases</a>
</ul>
<li><a href="#After_releasing">After releasing</a>
<li><a href="#GPL_releases">GPL Ghostscript releases</a>
<ul>
<li><a href="#GPL_code">GPL code</a>
<li><a href="#GPL_after_releasing">After releasing (GPL)</a>
</ul>
<li><a href="#Fonts">Fonts</a>
</ul></blockquote>
<!-- [1.2 end table of contents] =========================================== -->
<!-- [1.3 begin hint] ====================================================== -->
<p>For other information, see the <a href="Readme.htm">Ghostscript
overview</a> and the instructions on how to <a href="Make.htm">build
Ghostscript</a>.
<!-- [1.3 end hint] ======================================================== -->
<hr>
<!-- [1.0 end visible header] ============================================== -->
<!-- [2.0 begin contents] ================================================== -->
<h2><a name="Introduction"></a>Introduction</h2>
<p>
This document describes the process for making new Ghostscript releases.
Please note
that while the the license allows anyone to prepare and distribute
releases in accordance with its terms and conditions, this document is
really meant only to document the process used by Artifex Software, Inc.
However, the eventual purpose of this document is to describe
Ghostscript release procedures in enough detail that someone who knows
little about Ghostscript but is generally familiar with the platform on
which the procedure is being carried out can execute the procedures
correctly. So if you add or changing anything to/in this document,
be sure to specify all command lines, file names, etc. in explicit
detail.
<p>
File names below that don't include an explicit subdirectory name are in the
<b><tt>src</tt></b> subdirectory.
<p>
If you do plan to make your own distribution, please be aware of some items
you will want to change.
<ul>
<li>If you make any significant changes, please edit
<b><tt>gscdef.c</tt></b> to change <b><tt>GS_PRODUCTFAMILY</tt></b> and
<b><tt>GS_PRODUCT</tt></b> from "GPL Ghostscript" to something else,
in order to avoid confusion with Artifex releases.
<li>In the same file, you may also want to edit <b><tt>GS_COPYRIGHT</tt></b>
to add your own copyright notice (although you must not remove any
notice that is there).
<li>You will almost certainly want to edit <b><tt>version.mak</tt></b> to
change the revision date, <b><tt>GS_REVISIONDATE</tt></b>.
<li>If you want to change the release number, you must change it in all the
places listed under <a href="#Release_numbering">"Release numbering"</a>
below.
</ul>
<h2><a name="Servers"></a>Servers</h2>
<p>
The GPL Ghostscript files are maintained on sites accessible to
the public. One specific site hosts the active SVN repository for code,
data, and documentation, and the bug report data base; several sites
offer distributions with release numbers, intended for wider
distribution.
<h3><a name="Development_files"></a>Development sources and bug reports</h3>
<p>
The primary repository for GPL Ghostscript is <a
href="http://www.ghostscript.com/" class="offsite">ghostscript.com</a>.
Please check there first for any news about releases or current work,
and for information about where to download ghostscript and how to
access the mailing lists.
Development source access is through <a
href="http://svn.ghostscript.com/"
class="offsite">svn.ghostscript.com</a>.
<p>
It may also be helpful to
read the SourceForge Ghostscript home page (<a
href="http://sourceforge.net/projects/ghostscript/"
class="offsite">http://sourceforge.net/projects/ghostscript/</a>).
<h3><a name="Distribution"></a>Distribution</h3>
<p>
Stable, beta, and development releases are all available from
<blockquote>
<a
href="http://sourceforge.net/project/showfiles.php?group_id=1897"
class="offsite">http://sourceforge.net/project/showfiles.php?group_id=1897</a>
</blockquote>
<p>
Releases are also distributed from
<blockquote>
<a
href="ftp://mirror.cs.wisc.edu/pub/mirrors/ghost/GPL/"
class="offsite">ftp://mirror.cs.wisc.edu/pub/mirrors/ghost/GPL/</a> or
</blockquote>
<h2><a name="Release_numbering"></a>Release numbering</h2>
<p>
Ghostscript uses a two-part (major.minor) release number. The second part
of the release number is a 2-digit decimal fraction: it counts 00,
01, 02, and so on through 99.
<ul>
<li>Release numbers N.0x and N.5x indicate stable versions.
<li>Successive increments generally indicate bug fixes and minor enhancements.
<li>Development, testing and beta releases generally begin with a minor release number that is
a multiple of ten and increment from there.
</ul>
<p>
Release numbers appear in the following places in the Ghostscript files:
<ul>
<li>In <b><tt>lib/gs_init.ps</tt></b>, as an integer (release number x100) at the beginning of the
file just after the initial comment blocks.
<li>In <b><tt>src/version.mak</tt></b>, split into 3 lines.
<li>In <b><tt>doc/News.htm</tt></b>, in the two headers and their labels and at the very end in
the copyright footer.
<li>At the foot of most documenation files. However, these are updated mechanically from the value
in <b><tt>News.htm</tt></b> as part of the release process and do not need to be maintained
directly.
</ul>
<h3>Before a release</h3>
<p>
The current release number in the development code must be set to the desired value. The increment
from just after the previous release (see below) is sufficient for minor updates. In the case of
major changes or a new stable release, the number will need to be bumped; this is generally done
as the first step of preparing a new release.
<h3>After a release</h3>
<p>
After making a release the release number in the repository is
incremented. Thus versions built from svn are always marked with a
future (or unused) release number to avoid confusion.
<p>
Additionally, After an N.00 or N.50 stable release, a branch is made in svn so that development
can continue independently of changes to the stable series. When this happens, the minor release
number is incremented by 10 (or 20) on the development branch (and by 1 on the new stable branch,
as above) to avoid collisions.
<p>
While incrementing the release number after making a release may seem
counter-intuitive, it ensures that, at any given time, the version
number alone is sufficient to distinguish between the current SVN
state and a numbered release.
<h2><a name="Making_distributions"></a>Making distributions</h2>
<p>
This document only discusses source distributions. Source distributions
currently can only be made on Linux systems (but it probably wouldn't take
much work to support other Unix systems). Ghostscript as distributed also
often includes executables or other packages for the Windows and MacOS
environments, but upstream does not always produce these, and this
document does not discuss them.
<p>
To make a source distribution, you will need the scripts and data files in
the <b><tt>toolbin/</tt></b> directory. The instructions below generally
assume that you're invoking the relative to the top level of the source
tree.
To run the scripts, you will need reasonably current versions of Tcl,
freely available from Scriptics
(<a class="offsite" href="http://www.scriptics.com"><tt>http://www.scriptics.com</tt></a>), and
Python, freely available from <a class="offsite"
href="http://www.python.org"><tt>http://www.python.org</tt></a>.
<p>
The instructions below also refer to some files that are deliberately
omitted from the public distribution, because they are not freely
redistributable. You will need to provide similar files for your
environment.
<blockquote><pre>
<b><tt>data/*/*.ps</tt></b> (PostScript files) - needed for smoke testing
</pre></blockquote>
<h3><a name="Preparing_source"></a>Preparing the source code</h3>
<p>
If necessary, update the release number by incrementing it as described in
<a href="#Release_numbering">Release numbering</a> above.
<p>
Update references to the date for release:
<ul>
<li>In <b><tt>version.mak</tt></b>, the numeric date.
<li>In <b><tt>doc/News.htm</tt></b>, in two places, skipping the Id:
line. That is, in parentheses after the <tt>VERSION X.YY</tt> heading,
and in the copyright footer both the year and the release date.
<li>In <b><tt>src/dwsetup.rc</tt></b> and <b><tt>src/winint.mak</tt></b>,
update the year in the embedded copyright notice.
</ul>
<p>
We recommend using a UTC release date to avoid timezone skew.
<p>
Also in <b><tt>doc/News.htm</tt></b>, update the number of the highest
closed bug and the list of open bugs.
<p>
Check in <b><tt>gscdef.c</tt></b> that the definition of
<b><tt>GS_PRODUCT</tt></b> includes the appropriate one of "DEVELOPMENT
RELEASE", "BETA RELEASE", or neither, and does not include "SVN PRE-RELEASE".
<p>Run the source-consistency checks from the test suite:
<blockquote><pre>
toolbin/tests/check_all.py --gsroot=.
</pre></blockquote>
Where the argument of --gsroot is the path to the top level of the
source tree. Fix any problems it indicates, and commit them to svn.
<p>
Check for patched configuration parameters, <b><tt>#define TEST</tt></b>s,
version/date inconsistencies, and mismatches between the working directory
and the SVN repository by running:
<blockquote><pre>
toolbin/pre.tcl
</pre></blockquote>
<p>
This program compares the result of various greps against a check file,
writing the results of grep on one output file and the differences from the
check file on another. See the source code for the default file names. The
important one is the check file,
<b><tt>toolbin/pre.chk</tt></b>. <b><tt>pre.tcl</tt></b> also verifies
that the
right information is in the following places:
<ul>
<li>release number in <b><tt>man/*.1</tt></b>, <b><tt>doc/*.htm</tt></b>,
<b><tt>version.mak</tt></b>, <b><tt>doc/gs-vms.hlp</tt></b>,
<b><tt>lib/gs_init.ps</tt></b>
<li>revision date in <b><tt>man/*.1</tt></b>, <b><tt>doc/*.htm</tt></b>,
<b><tt>version.mak</tt></b>, <b><tt>doc/gs-vms.hlp</tt></b>
<li>copyright year (if necessary) in <b><tt>gscdef.c</tt></b>
<li>third-party library version number in <b><tt>*.mak</tt></b>
</ul>
<p>
If necessary, run
<blockquote><pre>
toolbin/pre.tcl update
</pre></blockquote>
<p>
to update the version and revision date in the doc files, and then run
<blockquote><pre>
toolbin/pre.tcl
</pre></blockquote>
<p>
again. To confirm that everything is updated. You may have to commit to
svn after the update to satify the script that all the dates are
correct.
<p>
Check the consistency of the source code with the makefiles by
running:
<blockquote><pre>
toolbin/gsmake.tcl check
</pre></blockquote>
This script assumes the top level makefile is named '<tt>makefile</tt>'.
<p>
Fix any problems and commit to svn.
<h3><a name="Testing"></a>Testing</h3>
<p>
Edit your top-level the Makefile to set
<blockquote><pre>
FEATURE_DEVS=$(FEATURE_DEVS_ALL)
COMPILE_INITS=1
</pre></blockquote>
<p>
This will help catch compilation problems.
<p>
Run
<blockquote><pre>
rm obj/*
make -j2 >& make.log
</pre></blockquote>
<p>
and look for warnings and errors in the log file.
<p>
Do a smoke test, updating the example paths as necessary:
<blockquote><pre>
unset GS_DEVICE GS_FONTPATH GS_LIB GS_OPTIONS
./bin/gs -I./lib -I./fonts -dNOPAUSE -dBATCH toolbin/smoke.ps
./bin/gs -I./lib -I./fonts -dNOPAUSE -dBATCH -sDEVICE=bitcmyk\
-sOutputFile=/dev/null -r600 -dBufferSpace=100000 toolbin/smoke.ps
</pre></blockquote>
<p>
This reads files named
<blockquote><pre>
<b><tt>data/misc/*.ps</tt></b>
<b><tt>data/ps/*.ps</tt></b>
<b><tt>data/psl2/*.ps</tt></b>
<b><tt>data/psl3/*.ps</tt></b>
</pre></blockquote>
<p>
(Edit <b><tt>toolbin/smoke.ps</tt></b> to use other test sets.)
Watch for crashes, unusual error messages, or anomalous displayed output.
If there are any problems, start over from the beginning of the process.
<p>
Undo the <b><tt>FEATURE_DEVS</tt></b> and <b><tt>COMPILE_INITS</tt></b>
edits.
<p>
Run
<blockquote><pre>
svn commit
</pre></blockquote>
<p>
to ensure the repository is up to date.
<h3><a name="Changelog"></a>Updating the changelog</h3>
<p>
Create a new changelog by running
<blockquote><pre>
svn log -rHEAD:<i>rev</i> --xml --verbose > doc/changelog.xml
</pre></blockquote>
where <i>rev</i> is the revision number of the branch point for the
previous release.
<p>
This consolidates all the commit logs since the previous release in a
readable format. You may also wish to remap user names in the
<author/> tags of the output to the real names of the developers.
<p>
Create the html-format changes and details documents as follows:
<blockquote><pre>
cd doc
../toolbin/split_changelog.py changelog.xml Changes.htm Details.htm
cd ..
</pre></blockquote>
<p>
The xml changelog file can now be deleted. Run
<blockquote><pre>
toolbin/makehist.tcl
</pre></blockquote>
<p>
This updates <b><tt>doc/History#.htm</tt></b> from
<b><tt>doc/News.htm</tt></b> and <b><tt>doc/Changes.htm</tt></b>.
<p><strong>N.B. this is currently broken; changelog updates have to be
manually copied into the History and Details files.</strong>
<p>
Then run
<blockquote><pre>
svn commit
</pre></blockquote>
<p>
again to check in the Changes and history files.
<h3><a name="Making_Tarballs"></a>Making the source distribution</h3>
<p>
First, tag the versions of the files in svn with the release version
number.
<blockquote>
<pre><tt>svn cp svn+ssh://svn.ghostscript.com/svn/ghostscript/branches/ghostscript-#.## \
svn+ssh://svn.ghostscript.com/svn/ghostscript/tags/ghostscript-#.##</tt></pre>
</blockquote>
If you've already tagged this release (e.g. in making an earlier
release candidate) you'll need to svn rm the old tree first. We
recommend just appending 'rc<i>n</i>' to the end of release candidate
tag names, or a '.<i>n</i>' tiny release number to post-release fixes.
<p>
Pull a fresh copy for distribution from the repository:
<blockquote><pre>
<tt>svn export http://svn.ghostscript.com:8080/ghostscript/tags/ghostscript-#.##</tt>
</pre></blockquote>
<p>
Generate the text versions of the README and PUBLIC documents:
<blockquote>
<pre><tt>cd ghostscript-#.##</tt>
<tt>lynx -dump -nolist doc/Readme.htm > doc/README</tt>
<tt>lynx -dump -nolist doc/Public.htm > doc/PUBLIC</tt></pre>
</blockquote>
<p>
Add copies of needed third-party libraries for the release. Versions
of the normally required ones are included in the repository so this
is only needed when doing special feature releases.
<p>
For the unix source distributions only, generate the configure
scripts. From the top level directory, run
<blockquote><pre><tt>./autogen.sh</tt>
<tt>make distclean</tt>
</pre></blockquote>
This should create links to <tt>configure.ac</tt> and
<tt>Makefile.in</tt> in the top level directory and
invoke autoconf to create the <tt>configure</tt> script.
<p>
Also run <tt>make distclean</tt> in the jasper subdir to
clean up any incidental config there.
<p>
Move back to directory containing the distribution code and make the
source archives with:
<blockquote><pre>
<tt>tar cvzf ghostscript-#.##.tar.gz ghostscript-#.##/*</tt>
<tt>zcat ghostscript-#.##.tar.gz | bzip2 -c > ghostscript-#.##.tar.bz2</tt>
</pre></blockquote>
<p>
This creates the files
<blockquote><pre>
<b><tt>ghostscript-#.##.tar.gz</tt></b> (main archive)
<b><tt>ghostscript-#.##.tar.bz2</tt></b> (main archive)
</pre></blockquote>
<p>
The important issue is that the tarballs unpack into a directory
of the same name, and that the code be a pristine copy without
build or .svn housekeeping files.
<p>
It is also customary to make a <tt>gs###src.zip</tt> archive for the
convenience of windows developers. See below.
<h3><a name="Testing_on_Windows"></a>Testing on Windows</h3>
<p>
For Windows testing, you will need, in addition to the files listed
under "<a href="#Preparing_source">Preparing the source</a>" above:
<blockquote><pre>
<b><tt>toolbin/makewin.tcl</tt></b>
</pre></blockquote>
<p>
The following procedures rely on a large number of MS-DOS batch scripts that
are not discussed here: they are unlikely to be generally useful.
<p>
Mount the Windows partition on <b><tt>/c</tt></b>, and create the
<b><tt>/c/work</tt></b> directory if needed.
<p>
Make the zip archive of all files needed for a Windows build, and copy it to
the Windows partition:
<blockquote><pre>
toolbin/makewin
cp gs###.zip /c/work
</pre></blockquote>
<p>
Boot into Windows. Unpack the archive:
<blockquote><pre>
cd \work
unzip -oq gs###.zip
gs###
</pre></blockquote>
<p>
The <b><tt>gs###.bat</tt></b> script creates some necessary directories,
sets up <b><tt>PATH</tt></b> and <b><tt>GS_LIB</tt></b> for testing, and
makes the <b><tt>gs#.##</tt></b> directory current.
<p>
Build with the Borland compiler:
<blockquote><pre>
config bcwin32
copy /y /b ..\gs\makefile
erase obj\*.*
make > bc.log
</pre></blockquote>
<p>
Smoke test the executables (both <b><tt>gswin32</tt></b> and
<b><tt>gswin32c</tt></b>), as described above for source distributions.
Then build with the Microsoft compiler:
<blockquote><pre>
config msvc32
copy /y /b ..\gs\makefile
erase obj\*.*
nmake > msvc.log
</pre></blockquote>
<p>
Smoke test these executables too.
<p>
Building with the Watcom compiler doesn't work, because the
<b><tt>wmake</tt></b> or <b><tt>wmakel</tt></b> program runs out of memory.
However, if it did work, this is how to do it:
<blockquote><pre>
config watcw32
copy /y /b ..\gs\makefile
erase obj\*.*
wmake -u > watc.log
</pre></blockquote>
<p>
Boot back into Linux. If testing in Windows revealed problems, edit the
source files as necessary, and go back to <a
href="#Preparing_source">"Preparing the source code."</a>
<h3><a name="Windows_distribution"></a>Building the Windows distribution</h3>
<p>
Extract the sources from <b><tt>ghostscript-N.NN.tar.gz</tt></b>
then repackage in a zip file as follows:
<blockquote>
<b><tt>zip -r temp.zip gsN.NN/LICENSE gsN.NN/doc gsN.NN/examples
gsN.NN/icclib gsN.NN/ijs gsN.NN/jasper gsN.NN/jbig2dec gsN.NN/jpeg
gsN.NN/lib gsN.NN/libpng gsN.NN/src gsN.NN/Resource gsN.NN/zlib</tt></b>
</blockquote>
Unzip converting the line endings to CRLF:
<blockquote>
<b><tt>unzip -a temp.zip<br>
del temp.zip</tt></b>
</blockquote>
Then finally zip up the sources to the distribution file:
<blockquote>
<b><tt>zip -9 -r -X gsNNNsrc.zip gsN.NN</tt></b>
</blockquote>
This method is reasonably portable, and does not convert binary
files such as
<b><tt><a href="../examples/annots.pdf">examples/annots.pdf</a></tt></b>.
<p>
Unzip <b><tt>gsNNNsrc.zip</tt></b>.
The directory must be named <b><tt>gsN.NN</tt></b>.
<p>
Extract the fonts <b><tt>ghostscript-fonts-std-#.##.tar.gz</tt></b>
into a directory <b><tt>fonts</tt></b> adjacent to the
<b><tt>gsN.NN</tt></b> directory.
The fonts are needed in this location for building
the distribution archive later.
<p>
You will need the command line Info-Zip zip program available from
<a href="http://www.info-zip.org/pub/infozip/">
http://www.info-zip.org/pub/infozip/</a>
Alternatively, the command line version of WinZip
(<b><tt>wzzip.exe</tt></b>) can be used by replacing the
Info-Zip command line options <b><tt>-9 -r</tt></b>
with <b><tt>-ex -P</tt></b> in
<b><tt><a href="../src/winint.mak">winint.mak</a></tt></b>.
<p>
You will need WinZip Self-Extractor for building the
self extracting archive. This is commercial software.
You may need to update the path <b><tt>WINZIPSE_XE</tt></b> in
<b><tt><a href="../src/winint.mak">winint.mak</a></tt></b>.
<p>
Unzip the jpeg, libpng and zlib libraries, then make ghostscript
as documented in <a href="Make.htm">Make.htm</a>.
<p>
Run the command <b><tt>nmake archive</tt></b>. This builds the distribution
archive <b><tt>gsNNNw32.exe</tt></b> and an ordinary zip file
<b><tt>gsNNNw32.zip</tt></b> in the parent directory.
If you do not have WinZip Self-Extractor, you can use
<b><tt>nmake zip</tt></b> to make <b><tt>gsNNNw32.zip</tt></b> only.
<h3><a name="Finishing_up"></a>Finishing up</h3>
<p>
Upload <b><tt>ghostscript-#.##.tar.*</tt></b> to SourceForge (by anonymous
FTP to <b><tt>upload.sourceforge.net</tt></b>, directory
<b><tt>/incoming</tt></b>), and then post it using the "File Release"
facility in the Ghostscript project. Put the release in the appropriate
package, usually "GPL Ghostscript".
If you are adding executable builds or source archives for other
platforms to an existing source release, please use the same release
date as the source release, not the current date.
<h3><a name="Beta_distributions"></a>Beta distributions</h3>
<p>
Do the steps for distributions in general.
<p>
Upload <b><tt>ghostscript-#.##.tar.*</tt></b> to
<b><tt>ftp://mirror.cs.wisc.edu/pub/mirrors/ghost/GPL/test</tt></b>.
<h3><a name="Public_releases"></a>Public releases</h3>
<p>
Do the steps for distributions in general.
<p>
Create a directory at
<b><tt>ftp://mirror.cs.wisc.edu/pub/mirrors/ghost/GPL/gs###/</tt></b>.
In that directory, store the following files:
<ul>
<li>Standard distribution files:
<blockquote><pre>
<b><tt>ghostscript-#.##.tar.gz</tt></b>
<b><tt>ghostscript-#.##.tar.bz2</tt></b>
</pre></blockquote>
<li>MS Windows source and executables:
<blockquote><pre>
<b><tt>gs###src.zip</tt></b>
<b><tt>gs###w32.exe</tt></b>
<b><tt>gs###w32.zip</tt></b>
</pre></blockquote>
<li>Third-party libraries, as links (upload these if not installed), where
<b><tt>$$$</tt></b> et al. refer to the version number of the library, which
should be the latest compatible release of the library and should be
consistent with the values of and version numbers specifically listed in
the makefiles.
<blockquote><pre>
<b><tt>jpegsrc.v$$.tar.gz</tt></b> -> <b><tt>../../3rdparty/jpegsrc.v$$.tar.gz</tt></b>
<b><tt>libpng-$.$.$.tar.gz</tt></b> -> <b><tt>../../3rdparty/libpng-$.$.$.tar.gz</tt></b>
<b><tt>zlib-$.$.$.tar.gz</tt></b> -> <b><tt>../../3rdparty/zlib-$.$.$.tar.gz</tt></b>
<b><tt>jpegsr$$.zip</tt></b> -> <b><tt>../../3rdparty/jpegsr$$.zip</tt></b>
<b><tt>lpng$$$.zip</tt></b> -> <b><tt>../../3rdparty/lpng$$$.zip</tt></b>
<b><tt>zlib$$$.zip</tt></b> -> <b><tt>../../3rdparty/zlib$$$.zip</tt></b>
</pre></blockquote>
In any case, the names of the links in the distribution directory should reflect
the original name of the upstream file.
<li>Fonts, where <b><tt>$.$$</tt></b> refers to the most recent version
number of the fonts:
<blockquote><pre>
<b><tt>ghostscript-fonts-other-$.$.tar.gz</tt></b> -> <b><tt>../fonts/ghostscript-fonts-other-$.$.tar.gz</tt></b>
<b><tt>ghostscript-fonts-std-$.$.tar.gz</tt></b> -> <b><tt>../fonts/ghostscript-fonts-std-$.$.tar.gz</tt></b>
</pre></blockquote>
</ul>
<p>
(Note that the link names are somewhat inconsistent: some of them retain the
version number of the file being referenced, and some of them use the
Ghostscript release number. This is a historical artifact that might be
changed someday.)
<p>
E-mail the release announcement using:
<blockquote><pre>
To: gs-announce
</pre></blockquote>
<p>
Edit the Web pages in svn and commit to reflect the new release.
The Wisconsin server should update automatically.
<h2><a name="After_releasing"></a>After releasing</h2>
<p>
Update the release number by incrementing it as described in <a
href="#Release_numbering">Release numbering</a> above.
<p>
In <b><tt>gscdef.c</tt></b>, edit the definition of
<b><tt>GS_PRODUCT</tt></b> to include "SVN PRE-RELEASE".
<p>
Edit <b><tt>doc/News.htm</tt></b> to remove all the content.
<h2><a name="Fonts"></a>Fonts</h2>
<p>
Artifex Software, Inc. distributes a package of the base 35 PostScript
fonts, and a package of other miscellaneous fonts.
<p>
To make the font packages, run the command
<blockquote><pre>
toolbin/makefonts #.##
</pre></blockquote>
<p>
This creates the following files:
<blockquote><pre>
ghostscript-fonts-std-#.##.tar.gz
ghostscript-fonts-other-#.##.tar.gz
</pre></blockquote>
<p>
The first two of these use the GPL, and should be uploaded to
<b><tt>ftp://mirror.cs.wisc.edu/pub/mirrors/ghost/fonts/</tt></b>.
<!-- [2.0 end contents] ==================================================== -->
<!-- [3.0 begin visible trailer] =========================================== -->
<hr>
<p>
<small>Copyright © 2000-2006 Artifex Software, Inc. All rights reserved.</small>
<p>
This software is provided AS-IS with no warranty, either express or
implied.
This software is distributed under license and may not be copied, modified
or distributed except as expressly authorized under the terms of that
license. Refer to licensing information at http://www.artifex.com/
or contact Artifex Software, Inc., 7 Mt. Lassen Drive - Suite A-134,
San Rafael, CA 94903, U.S.A., +1(415)492-9861, for further information.
<p>
<small>Ghostscript version 8.61, 19 November 2007
<!-- [3.0 end visible trailer] ============================================= -->
</body>
</html>
|
