X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Fnewrelease.html;h=6814b0eabbda4cd386f8c5d57dbfdccebe98c1b2;hb=1e5dbf87271fb9afca4ccd18a19c42e6d4d80dea;hp=5ff11fb599a716961070ffe48c4db91a3ba18372;hpb=2d6b5d2e894f920d7e376a9dc4fa436a8dbefcec;p=privoxy.git diff --git a/doc/webserver/developer-manual/newrelease.html b/doc/webserver/developer-manual/newrelease.html index 5ff11fb5..6814b0ea 100644 --- a/doc/webserver/developer-manual/newrelease.html +++ b/doc/webserver/developer-manual/newrelease.html @@ -1,11 +1,11 @@ +
Next | Privoxy version numbers consist of three numbers, - separated by dots, like in X.Y.Z, where: + separated by dots, like in X.Y.Z (e.g. 3.0.0), where:
Do NOT change a single bit, including, but not limited to version information after export from CVS. This is to make sure that all release packages, and with them, all future bug reports, are based on exactly the same code.
Warning |
Every significant release of Privoxy has included at least one + package that either had incorrect versions of files, missing files, + or incidental leftovers from a previous build process that gave + unknown numbers of users headaches to try to figure out what was + wrong. PLEASE, make sure you are using pristene sources, and are + following the prescribed process! + |
Please find additional instructions for the source tarball and the individual platform dependent binary packages below. And details @@ -374,9 +531,12 @@ NAME="PACK-GUIDELINES" >
Please keep these general guidelines in mind when putting together - your package. These apply to all platforms!
Privoxy requires write access to: all LICENSE (toplevel directory) +> (top-level directory) README (toplevel directory) +> (top-level directory) AUTHORS (toplevel directory) +> (top-level directory) man page (toplevel directory, Unix-like +> (top-level directory, Unix-like platforms only) Developer Manual - (doc/webserver/devel-manual) and ChangeLog - (toplevel directory). FAQ and the manuals are @@ -535,24 +698,31 @@ CLASS="FILENAME" to each other from parallel directories, and should be packaged that way. privoxy-index.html can also be + included and can serve as a focal point for docs and other links of + interest (and possibly renamed to index.html can also be included and - can serve as a focal point for docs and other links of interest. - This should be one level up from the manuals. There are two +>). + This should be one level up from the manuals. There is a link also + on this page to an HTMLized version of the man page. To avoid 404 for + this, it is in CVS as + doc/webserver/man-page/privoxy-man-page.html, + and should be included along with the manuals. There is also a css stylesheets that can be included for better presentation: p_doc.css and . This should be in the same directory + with p_web.css. - These should be in the same directory with - index.html, (i.e. one level up from the manual - directories). +>privoxy-index.html, (i.e. one level up from + the manual directories).
Other configuration files should be installed as the new defaults, - but all previously installed configuration files should be preserved - as backups. This is just good manners :-) +> Other configuration files (default.action and + default.filter) should be installed as the new + defaults, but all previously installed configuration files should be + preserved as backups. This is just good manners :-) These files are + likely to change between releases and contain important new features + and bug fixes.
Packagers should do a "clean" install of their + package after building it. So any previous installs should be + removed first to ensure the integrity of the newly built package. + Then run the package for a while to make sure there are no + obvious problems, before uploading. +
First, First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then run:
for SuSE.First, First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above).
6.3.4. OS/2First, First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then get the OS/2 Setup module:
cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setupcvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co os2setup
Choose the right operating system (not the Debian one). - When logged in, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then run:
First, First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then get the Windows setup module:
cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co winsetupcvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co winsetup
cd winsetup - makecd winsetup + make
First, First, make sure that you have freshly exported the right - version into an empty directory. (See "Building and releasing - packages" above). Then, run: -
make sure that you have freshly exported the + right version into an empty directory. (See + "Building and releasing packages" above). Then add a log + entry to debian/changelog, if it is not + already there, for example by running: +
cd current - autoheader && autoconf && ./configuredebchange -v 3.0.11-stable-1 "New upstream version" |
Then do FIXME. -
Then, run: +
dpkg-buildpackage -rfakeroot -us -uc -b |
This will create + ../privoxy_3.0.11-stable-1_i386.deb + which can be uploaded. To upload the package to Sourceforge, simply + issue +
make debian-upload |
First, First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing - packages" above). Then get the Mac OSX setup module: + packages" above). Then get the Mac OS X setup module:
cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co osxsetupcvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co osxsetup |
zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkgzip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg
Login to Sourceforge's compilefarm via ssh: +> Login to Sourceforge's compile-farm via ssh:
Home | Next |