@@ -229,8 +213,8 @@ body {
- Commit all files that were
- changed in the above steps!
+ Commit all files that
+ were changed in the above steps!
@@ -266,13 +250,13 @@ body {
GPL reasons the first package to be released is always the source
tarball.
- For all types of packages,
- including the source tarball, you
- must make sure that you build from clean sources by exporting the right
- version from CVS into an empty directory (just press return when
- asked for a password):
+ For all types
+ of packages, including the source tarball, you must make sure that you build from
+ clean sources by exporting the right version from CVS into an empty
+ directory (just press return when asked for a password):
-
+
@@ -285,15 +269,16 @@ body {
|
- 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.
+ 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 |
+ Warning |
@@ -318,16 +303,16 @@ body {
"PACK-GUIDELINES">6.3.1. Note on Privoxy Packaging
Please keep these general guidelines in mind when putting together
- your package. These apply to all platforms!
+ your package. These apply to all platforms!
-
Privoxy requires write access to: all
- *.action files, all logfiles, and the
- trust file. You will need to determine
- the best way to do this for your platform.
+ "emphasis">requires write access
+ to: all *.action files, all logfiles,
+ and the trust file. You will need to
+ determine the best way to do this for your platform.
-
@@ -451,11 +436,12 @@ body {
-
First, make sure that you have
- freshly exported the right version into an empty directory.
- (See "Building and releasing packages" above). Then run:
+ First, make sure that
+ you have freshly exported the right version into an empty
+ directory. (See "Building and releasing packages" above).
+ Then run:
-
+
@@ -468,7 +454,7 @@ body {
Then do:
-
+
@@ -480,7 +466,7 @@ body {
To upload the package to Sourceforge, simply issue
-
+
@@ -499,29 +485,31 @@ body {
- In following text, replace dist
- with either "rh" for Red Hat or
- "suse" for SuSE.
+ In following text, replace dist with either "rh" for Red Hat or "suse"
+ for SuSE.
- First, make sure that you have
- freshly exported the right version into an empty directory.
- (See "Building and releasing packages" above).
+ First, make sure that
+ you have freshly exported the right version into an empty
+ directory. (See "Building and releasing packages"
+ above).
As the only exception to not changing anything after export from
CVS, now examine the file privoxy-dist.spec
+ "FILENAME">privoxy-dist.spec
and make sure that the version information and the RPM release number
are correct. The RPM release numbers for each version start at one.
Hence it must be reset to one if this is the first RPM for dist which is built from version X.Y.Z. Check
- the dist which is built from version X.Y.Z.
+ Check the file list if unsure. Else, it must be set to the highest
already available RPM release number for that version plus one.
Then run:
-
+
@@ -534,11 +522,11 @@ body {
Then do
-
+
- make dist-dist
+ make dist-dist
|
@@ -546,19 +534,19 @@ body {
To upload the package to Sourceforge, simply issue
-
+
- make dist-upload rpm_packagerev
+ make dist-upload rpm_packagerev
|
- where rpm_packagerev is the RPM
- release number as determined above. Go to the displayed URL and
+ where rpm_packagerev is the
+ RPM release number as determined above. Go to the displayed URL and
release the file publicly on Sourceforge. Use the release notes and
change log from the source tarball package.
@@ -567,12 +555,12 @@ body {
- 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:
+ 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:
-
+
@@ -595,7 +583,7 @@ body {
directory. Edit the os2build.cmd file to set the final executable
filename. For example,
-
+
@@ -609,7 +597,7 @@ body {
release number matches in the PACKAGEID
section:
-
+
@@ -621,7 +609,7 @@ body {
You're now ready to build. Run:
-
+
@@ -644,7 +632,7 @@ body {
Login to Sourceforge's compilefarm via ssh:
-
+
@@ -655,11 +643,12 @@ body {
|
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:
+ logged in, make sure that
+ you have freshly exported the right version into an empty
+ directory. (See "Building and releasing packages" above).
+ Then run:
-
+
@@ -672,7 +661,7 @@ body {
Then run
-
+
@@ -698,12 +687,12 @@ body {
"_top">http://www.cygwin.com/). Run the following commands from
within a Cygwin bash shell.
- 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:
+ 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:
-
+
@@ -717,7 +706,7 @@ body {
controlled by winsetup/GNUmakefile. All you
need to do is:
-
+
@@ -739,17 +728,17 @@ body {
- First, 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:
+ First, 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:
-
+
- debchange -v 3.0.19-stable-1 "New upstream version"
+ debchange -v 3.0.21-UNRELEASED-1 "New upstream version"
|
@@ -757,7 +746,7 @@ body {
Then, run:
-
+
@@ -768,10 +757,10 @@ body {
|
This will create ../privoxy_3.0.19-stable-1_i386.deb which can be
+ "FILENAME">../privoxy_3.0.21-UNRELEASED-1_i386.deb which can be
uploaded. To upload the package to Sourceforge, simply issue
-
+
@@ -786,61 +775,136 @@ body {
- 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 OS X
- setup module:
+ 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 CVS 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 CVS
+ as follows into a folder parallel to the exported privoxy
+ source:
+
+
+
+
+
+ cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co OSXPackageBuilder
+
+ |
+
+
+
+ The module contains complete instructions on its usage in the
+ file OS X Package Builder HOWTO.txt.
+
+ Once the package(s) have been generated, you can then upload
+ them directly to the Files section of the Sourceforge project in
+ the Macintosh (OS X) folder. Each new version release of Privoxy
+ should have a new subfolder created in which to store its files.
+ Please ensure that the folder contains a readme file that 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 10.6 or higher.
+
+ Check out the module from CVS as follows into a folder parallel
+ to the exported privoxy source:
+
+
+
+
+
cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co osxsetup
- |
-
-
+ |
+
+
- Then run:
+ Then run:
-
-
-
-
+
+
+
+
cd osxsetup
build
- |
-
-
+ |
+
+
- This will run autoheader, autoconf and configure as
- well as make. Finally, it will copy over
- the necessary files to the ./osxsetup/files directory for further
- processing by PackageMaker.
+ This will run autoheader, autoconf and configure as
+ well as make. Finally, it will copy over
+ the necessary files to the ./osxsetup/files directory for further
+ processing by PackageMaker.
- Bring up PackageMaker with the PrivoxyPackage.pmsp definition
- file, modify the package name to match the release, and hit the
- "Create package" button. If you specify ./Privoxy.pkg as the output
- package name, you can then create the distributable zip file with the
- command:
+ Bring up PackageMaker with the PrivoxyPackage.pmsp definition
+ file, modify the package name to match the release, and hit the
+ "Create package" button. If you specify ./Privoxy.pkg as the output
+ package name, you can then create the distributable zip file with
+ the command:
-
-
-
-
+
+
+
+
zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg
- |
-
-
+ |
+
+
+
+ You can then upload this file directly to the Files section of
+ the Sourceforge project in the Macintosh (OS X) folder. Each new
+ version release of Privoxy should have a new subfolder created in
+ which to store its files. Please ensure that the folder contains a
+ readme file that makes it clear which version(s) of OS X the
+ 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 CVS as follows into a folder parallel
+ to the exported privoxy source:
+
+
+
+
+
+ cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co macsetup
+
+ |
+
+
- You can then upload privoxyosx_setup_x.y.z.zip 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.
+ The module contains complete instructions on its usage in its
+ README file. The end result will be the
+ exported version of Privoxy installed on the build machine.
+
@@ -849,7 +913,7 @@ body {
Login to Sourceforge's compile-farm via ssh:
-
+
@@ -860,11 +924,11 @@ body {
|
Choose the right operating system. 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:
+ "emphasis">make sure that you have freshly
+ exported the right version into an empty directory. (See
+ "Building and releasing packages" above). Then run:
-
+
@@ -877,7 +941,7 @@ body {
Then run:
-
+
@@ -898,11 +962,12 @@ body {
- First, make sure that you have
- freshly exported the right version into an empty directory.
- (See "Building and releasing packages" above). Then run:
+ First, make sure that
+ you have freshly exported the right version into an empty
+ directory. (See "Building and releasing packages" above).
+ Then run:
-
+
@@ -920,11 +985,12 @@ body {
- First, make sure that you have
- freshly exported the right version into an empty directory.
- (See "Building and releasing packages" above). Then run:
+ First, make sure that
+ you have freshly exported the right version into an empty
+ directory. (See "Building and releasing packages" above).
+ Then run:
-
+
@@ -944,7 +1010,7 @@ body {
Login to Sourceforge's compilefarm via ssh:
-
+
@@ -955,11 +1021,11 @@ body {
|
Choose the right operating system. 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:
+ "emphasis">make sure that you have freshly
+ exported the right version into an empty directory. (See
+ "Building and releasing packages" above). Then run:
-
+
@@ -972,7 +1038,7 @@ body {
Then run:
-
+
@@ -1024,7 +1090,7 @@ body {
column, and click Add Release. You will then
need to create a new release for your package, using the format of
$VERSION ($CODE_STATUS), e.g. 3.0.19 (beta).
+ "emphasis">3.0.21 (beta).
Now just follow the prompts. Be sure to add any appropriate Release
notes. You should see your freshly uploaded packages in
| | | | | | | | | | | | | | | | | | | |