Tag all files in Git with the version number with "cvs tag
+ Tag all files in Git with the version number with "git tag
v_X_Y_Z". Don't use vX_Y_Z, ver_X_Y_Z, v_X.Y.Z (won't work) etc.
mkdir dist # delete or choose different name if it already exists cd dist - cvs -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login - cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current+ git clone https://www.privoxy.org/git/privoxy.git + cd privoxy + git checkout v_X_Y_Z
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@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co os2setup- |
-
You will need a mix of development tools. The main compilation takes place with IBM Visual Age C++. Some - ancillary work takes place with GNU tools, available from various sources like hobbes.nmsu.edu. Specificially, - you will need autoheader, autoconf and sh tools. The packaging takes place with WarpIN, available from various sources, including its - home page: xworkplace.
-Change directory to the os2setup directory. Edit the os2build.cmd file to set the - final executable filename. For example,
-
- installExeName='privoxyos2_setup_X.Y.Z.exe'- |
-
Next, edit the IJB.wis file so the release number matches in the PACKAGEID section:
-
- PACKAGEID="Privoxy Team\Privoxy\Privoxy Package\X\Y\Z"- |
-
You're now ready to build. Run:
-
- os2build- |
-
You will find the WarpIN-installable executable in the ./files directory. Upload - this anonymously to uploads.sourceforge.net/incoming, create a release for it, and - you're done. Use the release notes and Change Log from the source tarball package.
-Login to Sourceforge's compilefarm via ssh:
- debchange -v 3.0.28-stable-1 "New upstream version"+ debchange -v 3.0.29-stable-1 "New upstream version" |
This will create ../privoxy_3.0.28-stable-1_i386.deb which can be uploaded. To +
This will create ../privoxy_3.0.29-stable-1_i386.deb which can be uploaded. To upload the package to Sourceforge, simply issue
First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above).
There are three modules available in the Git repository for use on Mac OS X, though technically only two of them generate a release (the other can be used to install from source).
The OSXPackageBuilder module generates OS X installer packages supporting all Macs running OS X 10.4 and above. Obtain it from Git as follows into a folder parallel to the exported privoxy source:
@@ -590,7 +543,7 @@ for-privoxy-version=3.0.11 makes it clear which package is for whichversion of OS X.This module is deprecated since the installer it generates places all Privoxy files in one folder in a non-standard location, and supports only Intel Macs running OS X @@ -632,7 +585,7 @@ for-privoxy-version=3.0.11 package supports.
The macsetup module is ideal if you wish to build and install Privoxy from source on a single machine.
Check out the module from Git as follows into a folder parallel to the exported privoxy source: