1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
2 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
6 Releasing a New Version
8 <meta name="GENERATOR" content=
9 "Modular DocBook HTML Stylesheet Version 1.79">
10 <link rel="HOME" title="Privoxy Developer Manual" href="index.html">
11 <link rel="PREVIOUS" title="Testing Guidelines" href="testing.html">
12 <link rel="NEXT" title="Update the Webserver" href=
13 "webserver-update.html">
14 <link rel="STYLESHEET" type="text/css" href="../p_doc.css">
15 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
17 <body class="SECT1" bgcolor="#EEEEEE" text="#000000" link="#0000FF" vlink=
18 "#840084" alink="#0000FF">
19 <div class="NAVHEADER">
20 <table summary="Header navigation table" width="100%" border="0"
21 cellpadding="0" cellspacing="0">
23 <th colspan="3" align="center">
24 Privoxy Developer Manual
28 <td width="10%" align="left" valign="bottom">
29 <a href="testing.html" accesskey="P">Prev</a>
31 <td width="80%" align="center" valign="bottom">
33 <td width="10%" align="right" valign="bottom">
34 <a href="webserver-update.html" accesskey="N">Next</a>
38 <hr align="LEFT" width="100%">
42 <a name="NEWRELEASE">6. Releasing a New Version</a>
45 When we release versions of <span class="APPLICATION">Privoxy</span>,
46 our work leaves our cozy secret lab and has to work in the cold
47 RealWorld[tm]. Once it is released, there is no way to call it back,
48 so it is very important that great care is taken to ensure that
49 everything runs fine, and not to introduce problems in the very last
53 So when releasing a new version, please adhere exactly to the
54 procedure outlined in this chapter.
57 The following programs are required to follow this process: <tt
58 class="FILENAME">ncftpput</tt> (ncftp), <tt class="FILENAME">scp,
59 ssh</tt> (ssh), <tt class="FILENAME">gmake</tt> (GNU's version of
64 <a name="VERSIONNUMBERS">6.1. Version numbers</a>
67 First you need to determine which version number the release will
68 have. <span class="APPLICATION">Privoxy</span> version numbers
69 consist of three numbers, separated by dots, like in X.Y.Z (e.g.
75 X, the version major, is rarely ever changed. It is increased
76 by one if turning a development branch into stable
77 substantially changes the functionality, user interface or
78 configuration syntax. Majors 1 and 2 were <span class=
79 "APPLICATION">Junkbuster</span>, and 3 will be the first stable
80 <span class="APPLICATION">Privoxy</span> release.
85 Y, the version minor, represents the branch within the major
86 version. At any point in time, there are two branches being
87 maintained: The stable branch, with an even minor, say, 2N, in
88 which no functionality is being added and only bug-fixes are
89 made, and 2N+1, the development branch, in which the further
90 development of <span class="APPLICATION">Privoxy</span> takes
91 place. This enables us to turn the code upside down and inside
92 out, while at the same time providing and maintaining a stable
93 version. The minor is reset to zero (and one) when the major is
94 incremented. When a development branch has matured to the point
95 where it can be turned into stable, the old stable branch 2N is
96 given up (i.e. no longer maintained), the former development
97 branch 2N+1 becomes the new stable branch 2N+2, and a new
98 development branch 2N+3 is opened.
103 Z, the point or sub version, represents a release of the
104 software within a branch. It is therefore incremented
105 immediately before each code freeze. In development branches,
106 only the even point versions correspond to actual releases,
107 while the odd ones denote the evolving state of the sources on
108 CVS in between. It follows that Z is odd on CVS in development
109 branches most of the time. There, it gets increased to an even
110 number immediately before a code freeze, and is increased to an
111 odd number again immediately thereafter. This ensures that
112 builds from CVS snapshots are easily distinguished from
113 released versions. The point version is reset to zero when the
117 Stable branches work a little differently, since there should
118 be little to no development happening in such branches.
119 Remember, only bugfixes, which presumably should have had some
120 testing before being committed. Stable branches will then have
121 their version reported as <tt class="LITERAL">0.0.0</tt>,
122 during that period between releases when changes are being
123 added. This is to denote that this code is <span class=
124 "emphasis"><i class="EMPHASIS">not for release</i></span>. Then
125 as the release nears, the version is bumped according: e.g. <tt
126 class="LITERAL">3.0.1 -> 0.0.0 -> 3.0.2</tt>.
132 In summary, the main CVS trunk is the development branch where new
133 features are being worked on for the next stable series. This
134 should almost always be where the most activity takes place. There
135 is always at least one stable branch from the trunk, e.g now it is
136 <tt class="LITERAL">3.0</tt>, which is only used to release stable
137 versions. Once the initial *.0 release of the stable branch has
138 been done, then as a rule, only bugfixes that have had prior
139 testing should be committed to the stable branch. Once there are
140 enough bugfixes to justify a new release, the version of this
141 branch is again incremented Example: 3.0.0 -> 3.0.1 -> 3.0.2,
142 etc are all stable releases from within the stable branch. 3.1.x is
143 currently the main trunk, and where work on 3.2.x is taking place.
144 If any questions, please post to the devel list <span class=
145 "emphasis"><i class="EMPHASIS">before</i></span> committing to a
149 Developers should remember too that if they commit a bugfix to the
150 stable branch, this will more than likely require a separate
151 submission to the main trunk, since these are separate development
152 trees within CVS. If you are working on both, then this would
153 require at least two separate check outs (i.e main trunk, <span
154 class="emphasis"><i class="EMPHASIS">and</i></span> the stable
155 release branch, which is <tt class="LITERAL">v_3_0_branch</tt> at
161 <a name="BEFORERELEASE">6.2. Before the Release: Freeze</a>
164 The following <span class="emphasis"><i class="EMPHASIS">must be
165 done by one of the developers</i></span> prior to each new release.
172 Make sure that everybody who has worked on the code in the last
173 couple of days has had a chance to yell <span class=
174 "QUOTE">"no!"</span> in case they have pending changes/fixes in
175 their pipelines. Announce the freeze so that nobody will
176 interfere with last minute changes.
181 Increment the version number (point from odd to even in
182 development branches!) in <tt class=
183 "FILENAME">configure.in</tt> and update the code status
184 (CODE_STATUS="xxx") to one of "alpha", "beta" or "stable".
185 Rebuild configure and GNUMakefile to make sure the updated
186 values are being used.
191 Use the dok-release target to update the sgml documentation
197 If action file processing has changed and is not
198 backward-compatible, make sure the "for-privoxy-version=x.y.z"
199 minimum version number in default.action.master has been
202 <table border="0" bgcolor="#E0E0E0" width="90%">
205 <pre class="PROGRAMLISTING">
207 #############################################################################
208 #MASTER# COMMENT: The minimum Privoxy version:
209 for-privoxy-version=3.0.11
217 All documentation should be rebuild after the version bump.
218 Finished docs should be then be committed to CVS (for those
219 without the ability to build these). Some docs may require
220 rather obscure processing tools. <tt class=
221 "FILENAME">config</tt>, the man page (and the html version of
222 the man page) fall in this category. README, the man page,
223 AUTHORS, and config should all also be committed to CVS for
224 other packagers. The formal docs should be uploaded to the
225 webserver. See the Section "Updating the webserver" in this
231 The <i class="CITETITLE">User Manual</i> is also used for
232 context sensitive help for the CGI editor. This is version
233 sensitive, so that the user will get appropriate help for
234 his/her release. So with each release a fresh version should be
235 uploaded to the webserver (this is in addition to the main <i
236 class="CITETITLE">User Manual</i> link from the main page since
237 we need to keep manuals for various versions available). The
238 CGI pages will link to something like <tt class=
239 "LITERAL">http://privoxy.org/$(VERSION)/user-manual/</tt>. This
240 will need to be updated for each new release. There is no
241 Makefile target for this at this time!!! It needs to be done
247 All developers should look at the <tt class=
248 "FILENAME">ChangeLog</tt> and make sure noteworthy changes are
254 <span class="emphasis"><i class="EMPHASIS">Commit all files
255 that were changed in the above steps!</i></span>
260 Tag all files in CVS with the version number with <span class=
261 "QUOTE">"<b class="COMMAND">cvs tag v_X_Y_Z</b>"</span>. Don't
262 use vX_Y_Z, ver_X_Y_Z, v_X.Y.Z (won't work) etc.
267 If the release was in a development branch, increase the point
268 version from even to odd (X.Y.(Z+1)) again in <tt class=
269 "FILENAME">configure.in</tt> and commit your change.
274 On the webserver, copy the user manual to a new top-level
275 directory called <tt class="FILENAME">X.Y.Z</tt>. This ensures
276 that help links from the CGI pages, which have the version as a
277 prefix, will go into the right version of the manual. If this
278 is a development branch release, also symlink <tt class=
279 "FILENAME">X.Y.(Z-1)</tt> to <tt class="FILENAME">X.Y.Z</tt>
280 and <tt class="FILENAME">X.Y.(Z+1)</tt> to <tt class=
281 "FILENAME">.</tt> (i.e. dot).
288 <a name="THERELEASE">6.3. Building and Releasing the Packages</a>
291 Now the individual packages can be built and released. Note that
292 for GPL reasons the first package to be released is always the
296 For <span class="emphasis"><i class="EMPHASIS">all</i></span> types
297 of packages, including the source tarball, <span class=
298 "emphasis"><i class="EMPHASIS">you must make sure that you build
299 from clean sources by exporting the right version from CVS into an
300 empty directory</i></span> (just press return when asked for a
305 <table border="0" bgcolor="#E0E0E0" width="100%">
308 <pre class="PROGRAMLISTING">
309 mkdir dist # delete or choose different name if it already exists
311 cvs -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login
312 cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
319 <span class="emphasis"><i class="EMPHASIS">Do NOT change</i></span>
320 a single bit, including, but not limited to version information
321 after export from CVS. This is to make sure that all release
322 packages, and with them, all future bug reports, are based on
323 exactly the same code.
325 <div class="WARNING">
326 <table class="WARNING" border="1" width="100%">
335 Every significant release of Privoxy has included at least
336 one package that either had incorrect versions of files,
337 missing files, or incidental leftovers from a previous
338 build process that gave unknown numbers of users headaches
339 to try to figure out what was wrong. PLEASE, make sure you
340 are using pristene sources, and are following the
348 Please find additional instructions for the source tarball and the
349 individual platform dependent binary packages below. And details on
350 the Sourceforge release process below that.
354 <a name="PACK-GUIDELINES">6.3.1. Note on Privoxy Packaging</a>
357 Please keep these general guidelines in mind when putting
358 together your package. These apply to <span class="emphasis"><i
359 class="EMPHASIS">all</i></span> platforms!
366 <span class="APPLICATION">Privoxy</span> <span class=
367 "emphasis"><i class="EMPHASIS">requires</i></span> write
368 access to: all <tt class="FILENAME">*.action</tt> files, all
369 logfiles, and the <tt class="FILENAME">trust</tt> file. You
370 will need to determine the best way to do this for your
376 Please include up to date documentation. At a bare minimum:
382 <tt class="FILENAME">LICENSE</tt> (top-level directory)
391 <tt class="FILENAME">README</tt> (top-level directory)
400 <tt class="FILENAME">AUTHORS</tt> (top-level directory)
409 <tt class="FILENAME">man page</tt> (top-level
410 directory, Unix-like platforms only)
419 <tt class="FILENAME">The User Manual</tt>
420 (doc/webserver/user-manual/)
429 <tt class="FILENAME">FAQ</tt> (doc/webserver/faq/)
435 Also suggested: <tt class="FILENAME">Developer Manual</tt>
436 (doc/webserver/developer-manual) and <tt class=
437 "FILENAME">ChangeLog</tt> (top-level directory). <tt class=
438 "FILENAME">FAQ</tt> and the manuals are HTML docs. There are
439 also text versions in <tt class="FILENAME">doc/text/</tt>
440 which could conceivably also be included.
443 The documentation has been designed such that the manuals are
444 linked to each other from parallel directories, and should be
445 packaged that way. <tt class=
446 "FILENAME">privoxy-index.html</tt> can also be included and
447 can serve as a focal point for docs and other links of
448 interest (and possibly renamed to <tt class=
449 "FILENAME">index.html</tt>). This should be one level up from
450 the manuals. There is a link also on this page to an HTMLized
451 version of the man page. To avoid 404 for this, it is in CVS
453 "FILENAME">doc/webserver/man-page/privoxy-man-page.html</tt>,
454 and should be included along with the manuals. There is also
455 a css stylesheets that can be included for better
456 presentation: <tt class="FILENAME">p_doc.css</tt>. This
457 should be in the same directory with <tt class=
458 "FILENAME">privoxy-index.html</tt>, (i.e. one level up from
459 the manual directories).
464 <tt class="FILENAME">user.action</tt> and <tt class=
465 "FILENAME">user.filter</tt> are designed for local
466 preferences. Make sure these do not get overwritten! <tt
467 class="FILENAME">config</tt> should not be overwritten
468 either. This has especially important configuration data in
469 it. <tt class="FILENAME">trust</tt> should be left in tact as
475 Other configuration files (<tt class=
476 "FILENAME">default.action</tt> and <tt class=
477 "FILENAME">default.filter</tt>) should be installed as the
478 new defaults, but all previously installed configuration
479 files should be preserved as backups. This is just good
480 manners :-) These files are likely to change between releases
481 and contain important new features and bug fixes.
486 Please check platform specific notes in this doc, if you
487 haven't done <span class="QUOTE">"Privoxy"</span> packaging
488 before for other platform specific issues. Conversely, please
489 add any notes that you know are important for your platform
490 (or contact one of the doc maintainers to do this if you
496 Packagers should do a <span class="QUOTE">"clean"</span>
497 install of their package after building it. So any previous
498 installs should be removed first to ensure the integrity of
499 the newly built package. Then run the package for a while to
500 make sure there are no obvious problems, before uploading.
507 <a name="NEWRELEASE-TARBALL">6.3.2. Source Tarball</a>
510 First, <span class="emphasis"><i class="EMPHASIS">make sure that
511 you have freshly exported the right version into an empty
512 directory</i></span>. (See "Building and releasing packages"
517 <table border="0" bgcolor="#E0E0E0" width="100%">
520 <pre class="PROGRAMLISTING">
522 autoheader && autoconf && ./configure
533 <table border="0" bgcolor="#E0E0E0" width="100%">
536 <pre class="PROGRAMLISTING">
544 To upload the package to Sourceforge, simply issue
548 <table border="0" bgcolor="#E0E0E0" width="100%">
551 <pre class="PROGRAMLISTING">
559 Go to the displayed URL and release the file publicly on
560 Sourceforge. For the change log field, use the relevant section
561 of the <tt class="FILENAME">ChangeLog</tt> file.
566 <a name="NEWRELEASE-RPM">6.3.3. SuSE, Conectiva or Red Hat
570 In following text, replace <tt class=
571 "REPLACEABLE"><i>dist</i></tt> with either <span class=
572 "QUOTE">"rh"</span> for Red Hat or <span class=
573 "QUOTE">"suse"</span> for SuSE.
576 First, <span class="emphasis"><i class="EMPHASIS">make sure that
577 you have freshly exported the right version into an empty
578 directory</i></span>. (See "Building and releasing packages"
582 As the only exception to not changing anything after export from
583 CVS, now examine the file <tt class="FILENAME">privoxy-</tt><tt
584 class="REPLACEABLE"><i>dist</i></tt><tt class=
585 "FILENAME">.spec</tt> and make sure that the version information
586 and the RPM release number are correct. The RPM release numbers
587 for each version start at one. Hence it must be reset to one if
588 this is the first RPM for <tt class=
589 "REPLACEABLE"><i>dist</i></tt> which is built from version X.Y.Z.
591 "https://sourceforge.net/project/showfiles.php?group_id=11118"
592 target="_top">file list</a> if unsure. Else, it must be set to
593 the highest already available RPM release number for that version
601 <table border="0" bgcolor="#E0E0E0" width="100%">
604 <pre class="PROGRAMLISTING">
606 autoheader && autoconf && ./configure
617 <table border="0" bgcolor="#E0E0E0" width="100%">
620 <pre class="PROGRAMLISTING">
621 make <tt class="REPLACEABLE"><i>dist</i></tt>-dist
628 To upload the package to Sourceforge, simply issue
632 <table border="0" bgcolor="#E0E0E0" width="100%">
635 <pre class="PROGRAMLISTING">
636 make <tt class="REPLACEABLE"><i>dist</i></tt>-upload <tt class=
637 "REPLACEABLE"><i>rpm_packagerev</i></tt>
644 where <tt class="REPLACEABLE"><i>rpm_packagerev</i></tt> is the
645 RPM release number as determined above. Go to the displayed URL
646 and release the file publicly on Sourceforge. Use the release
647 notes and change log from the source tarball package.
652 <a name="NEWRELEASE-OS2">6.3.4. OS/2</a>
655 First, <span class="emphasis"><i class="EMPHASIS">make sure that
656 you have freshly exported the right version into an empty
657 directory</i></span>. (See "Building and releasing packages"
658 above). Then get the OS/2 Setup module:
662 <table border="0" bgcolor="#E0E0E0" width="100%">
665 <pre class="PROGRAMLISTING">
666 cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co os2setup
673 You will need a mix of development tools. The main compilation
674 takes place with IBM Visual Age C++. Some ancillary work takes
675 place with GNU tools, available from various sources like
676 hobbes.nmsu.edu. Specificially, you will need <tt class=
677 "FILENAME">autoheader</tt>, <tt class="FILENAME">autoconf</tt>
678 and <tt class="FILENAME">sh</tt> tools. The packaging takes place
679 with WarpIN, available from various sources, including its home
680 page: <a href="http://www.xworkplace.org/" target=
681 "_top">xworkplace</a>.
684 Change directory to the <tt class="FILENAME">os2setup</tt>
685 directory. Edit the os2build.cmd file to set the final executable
686 filename. For example,
690 <table border="0" bgcolor="#E0E0E0" width="100%">
693 <pre class="PROGRAMLISTING">
694 installExeName='privoxyos2_setup_X.Y.Z.exe'
701 Next, edit the <tt class="FILENAME">IJB.wis</tt> file so the
702 release number matches in the <tt class="FILENAME">PACKAGEID</tt>
707 <table border="0" bgcolor="#E0E0E0" width="100%">
710 <pre class="PROGRAMLISTING">
711 PACKAGEID="Privoxy Team\Privoxy\Privoxy Package\X\Y\Z"
718 You're now ready to build. Run:
722 <table border="0" bgcolor="#E0E0E0" width="100%">
725 <pre class="PROGRAMLISTING">
733 You will find the WarpIN-installable executable in the <tt class=
734 "FILENAME">./files</tt> directory. Upload this anonymously to <tt
735 class="FILENAME">uploads.sourceforge.net/incoming</tt>, create a
736 release for it, and you're done. Use the release notes and Change
737 Log from the source tarball package.
742 <a name="NEWRELEASE-SOLARIS">6.3.5. Solaris</a>
745 Login to Sourceforge's compilefarm via ssh:
749 <table border="0" bgcolor="#E0E0E0" width="100%">
752 <pre class="PROGRAMLISTING">
753 ssh cf.sourceforge.net
760 Choose the right operating system (not the Debian one). When
761 logged in, <span class="emphasis"><i class="EMPHASIS">make sure
762 that you have freshly exported the right version into an empty
763 directory</i></span>. (See "Building and releasing packages"
768 <table border="0" bgcolor="#E0E0E0" width="100%">
771 <pre class="PROGRAMLISTING">
773 autoheader && autoconf && ./configure
784 <table border="0" bgcolor="#E0E0E0" width="100%">
787 <pre class="PROGRAMLISTING">
795 which creates a gzip'ed tar archive. Sadly, you cannot use <b
796 class="COMMAND">make solaris-upload</b> on the Sourceforge
797 machine (no ncftpput). You now have to manually upload the
798 archive to Sourceforge's ftp server and release the file
799 publicly. Use the release notes and Change Log from the source
805 <a name="NEWRELEASE-WINDOWS">6.3.6. Windows</a>
809 "http://www.fruitbat.org/Cygwin/index.html#cygwincirca" target=
810 "_top">Cygwin Time Machine</a> to install the last 1.5 version of
811 Cygwin. Run the following commands from within the Cygwin 1.5
815 First, <span class="emphasis"><i class="EMPHASIS">make sure that
816 you have freshly exported the right version into an empty
817 directory</i></span>. (See "Building and releasing packages"
818 above). Then get the Windows setup module:
822 <table border="0" bgcolor="#E0E0E0" width="100%">
825 <pre class="PROGRAMLISTING">
826 cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co winsetup
833 Then you can build the package. This is fully automated, and is
834 controlled by <tt class="FILENAME">winsetup/GNUmakefile</tt>. All
839 <table border="0" bgcolor="#E0E0E0" width="100%">
842 <pre class="PROGRAMLISTING">
851 Now you can manually rename <tt class=
852 "FILENAME">privoxy_setup.exe</tt> to <tt class=
853 "FILENAME">privoxy_setup_X_Y_Z.exe</tt>, and upload it to
854 SourceForge. When releasing the package on SourceForge, use the
855 release notes and Change Log from the source tarball package.
860 <a name="NEWRELEASE-DEBIAN">6.3.7. Debian</a>
863 First, <span class="emphasis"><i class="EMPHASIS">make sure that
864 you have freshly exported the right version into an empty
865 directory</i></span>. (See "Building and releasing packages"
866 above). Then add a log entry to <tt class=
867 "FILENAME">debian/changelog</tt>, if it is not already there, for
872 <table border="0" bgcolor="#E0E0E0" width="100%">
875 <pre class="PROGRAMLISTING">
876 debchange -v 3.0.26-stable-1 "New upstream version"
887 <table border="0" bgcolor="#E0E0E0" width="100%">
890 <pre class="PROGRAMLISTING">
891 dpkg-buildpackage -rfakeroot -us -uc -b
898 This will create <tt class=
899 "FILENAME">../privoxy_3.0.26-stable-1_i386.deb</tt> which can be
900 uploaded. To upload the package to Sourceforge, simply issue
904 <table border="0" bgcolor="#E0E0E0" width="100%">
907 <pre class="PROGRAMLISTING">
916 <a name="NEWRELEASE-MACOSX">6.3.8. Mac OS X</a>
919 First, <span class="emphasis"><i class="EMPHASIS">make sure that
920 you have freshly exported the right version into an empty
921 directory</i></span>. (See "Building and releasing packages"
925 There are three modules available in the CVS repository for use
926 on Mac OS X, though technically only two of them generate a
927 release (the other can be used to install from source).
931 <a name="OS-X-OSXPACKAGEBUILDER-MODULE">6.3.8.1.
932 OSXPackageBuilder module</a>
935 The OSXPackageBuilder module generates OS X installer packages
936 supporting all Macs running OS X 10.4 and above. Obtain it from
937 CVS as follows into a folder parallel to the exported privoxy
940 <table border="0" bgcolor="#E0E0E0" width="100%">
943 <pre class="PROGRAMLISTING">
944 cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co OSXPackageBuilder
951 The module contains complete instructions on its usage in the
952 file <tt class="FILENAME">OS X Package Builder HOWTO.txt</tt>.
955 Once the package(s) have been generated, you can then upload
956 them directly to the Files section of the Sourceforge project
957 in the Macintosh (OS X) folder. Each new version release of
958 Privoxy should have a new subfolder created in which to store
959 its files. Please ensure that the folder contains a readme file
960 that makes it clear which package is for whichversion of OS X.
965 <a name="OS-X-OSXSETUP-MODULE">6.3.8.2. osxsetup module
969 <span class="emphasis"><i class="EMPHASIS">This module is
970 deprecated since the installer it generates places all Privoxy
971 files in one folder in a non-standard location, and supports
972 only Intel Macs running OS X 10.6 or higher.</i></span>
975 Check out the module from CVS as follows into a folder parallel
976 to the exported privoxy source:
978 <table border="0" bgcolor="#E0E0E0" width="100%">
981 <pre class="PROGRAMLISTING">
982 cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co osxsetup
993 <table border="0" bgcolor="#E0E0E0" width="100%">
996 <pre class="PROGRAMLISTING">
1005 This will run <tt class="FILENAME">autoheader</tt>, <tt class=
1006 "FILENAME">autoconf</tt> and <tt class=
1007 "FILENAME">configure</tt> as well as <tt class=
1008 "FILENAME">make</tt>. Finally, it will copy over the necessary
1009 files to the ./osxsetup/files directory for further processing
1010 by <tt class="FILENAME">PackageMaker</tt>.
1013 Bring up PackageMaker with the PrivoxyPackage.pmsp definition
1014 file, modify the package name to match the release, and hit the
1015 "Create package" button. If you specify ./Privoxy.pkg as the
1016 output package name, you can then create the distributable zip
1017 file with the command:
1021 <table border="0" bgcolor="#E0E0E0" width="100%">
1024 <pre class="PROGRAMLISTING">
1025 zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg
1032 You can then upload this file directly to the Files section of
1033 the Sourceforge project in the Macintosh (OS X) folder. Each
1034 new version release of Privoxy should have a new subfolder
1035 created in which to store its files. Please ensure that the
1036 folder contains a readme file that makes it clear which
1037 version(s) of OS X the package supports.
1042 <a name="OS-X-MACSETUP-MODULE">6.3.8.3. macsetup module</a>
1045 The macsetup module is ideal if you wish to build and install
1046 Privoxy from source on a single machine.
1049 Check out the module from CVS as follows into a folder parallel
1050 to the exported privoxy source:
1052 <table border="0" bgcolor="#E0E0E0" width="100%">
1055 <pre class="PROGRAMLISTING">
1056 cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co macsetup
1063 The module contains complete instructions on its usage in its
1064 <tt class="FILENAME">README</tt> file. The end result will be
1065 the exported version of Privoxy installed on the build machine.
1071 <a name="NEWRELEASE-FREEBSD">6.3.9. FreeBSD</a>
1074 Update the www/privoxy port and submit a diff upstream. For
1075 details see the <a href=
1076 "https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/"
1077 target="_top">FreeBSD Porter's Handbook</a>.
1083 <a name="RELEASING">6.4. Uploading and Releasing Your Package</a>
1086 After the package is ready, it is time to upload it to SourceForge,
1087 and go through the release steps. The upload is done via FTP:
1094 Upload to: <a href="ftp://upload.sourceforge.net/incoming"
1095 target="_top">ftp://upload.sourceforge.net/incoming</a>
1100 user: <tt class="LITERAL">anonymous</tt>
1105 password: <tt class=
1106 "LITERAL">ijbswa-developers@lists.sourceforge.net</tt>
1112 Or use the <b class="COMMAND">make</b> targets as described above.
1115 Once this done go to <a href=
1116 "https://sourceforge.net/project/admin/editpackages.php?group_id=11118"
1118 "_top">https://sourceforge.net/project/admin/editpackages.php?group_id=11118</a>,
1119 making sure you are logged in. Find your target platform in the
1120 second column, and click <tt class="LITERAL">Add Release</tt>. You
1121 will then need to create a new release for your package, using the
1122 format of <tt class="LITERAL">$VERSION ($CODE_STATUS)</tt>, e.g.
1123 <span class="emphasis"><i class="EMPHASIS">3.0.26
1127 Now just follow the prompts. Be sure to add any appropriate Release
1128 notes. You should see your freshly uploaded packages in <span
1129 class="QUOTE">"Step 2. Add Files To This Release"</span>. Check the
1130 appropriate box(es). Remember at each step to hit the <span class=
1131 "QUOTE">"Refresh/Submit"</span> buttons! You should now see your
1132 file(s) listed in Step 3. Fill out the forms with the appropriate
1133 information for your platform, being sure to hit <span class=
1134 "QUOTE">"Update"</span> for each file. If anyone is monitoring your
1135 platform, check the <span class="QUOTE">"email"</span> box at the
1136 very bottom to notify them of the new package. This should do it!
1139 If you have made errors, or need to make changes, you can go
1140 through essentially the same steps, but select <tt class=
1141 "LITERAL">Edit Release</tt>, instead of <tt class="LITERAL">Add
1147 <a name="AFTERRELEASE">6.5. After the Release</a>
1150 When all (or: most of the) packages have been uploaded and made
1151 available, send an email to the <a href=
1152 "mailto:privoxy-announce@lists.privoxy.org" target="_top">announce
1153 mailing list</a>, Subject: "Version X.Y.Z available for download".
1154 Be sure to include the <a href=
1155 "https://sourceforge.net/project/showfiles.php?group_id=11118"
1156 target="_top">download location</a>, the release notes and the
1157 Changelog. Also, post an updated News item on the project page
1158 Sourceforge, and update the Home page and docs linked from the Home
1159 page (see below). Other news sites and release oriented sites, such
1160 as Freshmeat, should also be notified.
1164 <div class="NAVFOOTER">
1165 <hr align="LEFT" width="100%">
1166 <table summary="Footer navigation table" width="100%" border="0"
1167 cellpadding="0" cellspacing="0">
1169 <td width="33%" align="left" valign="top">
1170 <a href="testing.html" accesskey="P">Prev</a>
1172 <td width="34%" align="center" valign="top">
1173 <a href="index.html" accesskey="H">Home</a>
1175 <td width="33%" align="right" valign="top">
1176 <a href="webserver-update.html" accesskey="N">Next</a>
1180 <td width="33%" align="left" valign="top">
1183 <td width="34%" align="center" valign="top">
1186 <td width="33%" align="right" valign="top">
1187 Update the Webserver