X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fdeveloper-manual.sgml;h=e5998abb57f2be7e9354b1bf279de913c870224d;hp=a95cf5e9132a29e0e9f8a415fe5d1c625fc88950;hb=1e978c46c5b5b21a8a283a9d62069cfc300ea0d1;hpb=c69d804f689724964dcc46afb1e61a72373bda15
diff --git a/doc/source/developer-manual.sgml b/doc/source/developer-manual.sgml
index a95cf5e9..e5998abb 100644
--- a/doc/source/developer-manual.sgml
+++ b/doc/source/developer-manual.sgml
@@ -5,8 +5,8 @@
-
-
+
+
@@ -21,9 +21,9 @@
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: developer-manual.sgml,v 2.58 2014/05/26 10:48:39 fabiankeil Exp $
+ $Id: developer-manual.sgml,v 2.70 2016/05/22 12:42:11 fabiankeil Exp $
- Copyright (C) 2001-2012 Privoxy Developers http://www.privoxy.org/
+ Copyright (C) 2001-2016 Privoxy Developers https://www.privoxy.org/
See LICENSE.
========================================================================
@@ -42,14 +42,14 @@
- Copyright
- &my-copy; 2001-2013 by
- Privoxy Developers
+ Copyright
+ &my-copy; 2001-2016 by
+ Privoxy Developers
- $Id: developer-manual.sgml,v 2.58 2014/05/26 10:48:39 fabiankeil Exp $
+ $Id: developer-manual.sgml,v 2.70 2016/05/22 12:42:11 fabiankeil Exp $
-
-
@@ -137,7 +134,7 @@ Hal.
Quickstart to Privoxy Development
The first step is to join the developer's mailing list.
+ url="https://lists.privoxy.org/mailman/listinfo/privoxy-devel">privoxy-devel mailing list.
You can submit your ideas, or even better patches. Patches are best
submitted to the Sourceforge tracker set up for this purpose, but
can be sent to the list for review too.
@@ -168,11 +165,8 @@ Hal.
Access to CVS
The project's CVS repository is hosted on
- SourceForge.
- Please refer to the chapters 6 and 7 in
- SF's site
- documentation for the technical access details for your
- operating system. For historical reasons, the CVS server is
+ SourceForge.
+ For historical reasons, the CVS server is
called ijbswa.cvs.sourceforge.net, the repository is
called ijbswa, and the source tree module is called
current.
@@ -186,7 +180,8 @@ Hal.
mentioned, the sources are in the current
module
. Other modules are present for platform specific
issues. There is a webview of the CVS hierarchy at http://ijbswa.cvs.sourceforge.net/ijbswa/,
+ url="http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/"
+ >http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/,
which might help with visualizing how these pieces fit together.
d$";
* Purpose : (Fill me in with a good description!)
*
* Copyright : Written by and Copyright (C) 2001-2009
- * the Privoxy team. http://www.privoxy.org/
+ * the Privoxy team. https://www.privoxy.org/
*
* This program is free software; you can redistribute it
* and/or modify it under the terms of the GNU General
@@ -1862,7 +1857,7 @@ const char FILENAME_h_rcs[] = FILENAME_H_VERSION;
* Purpose : (Fill me in with a good description!)
*
* Copyright : Written by and Copyright (C) 2001-2009
- * the Privoxy team. http://www.privoxy.org/
+ * the Privoxy team. https://www.privoxy.org/
*
* This program is free software; you can redistribute it
* and/or modify it under the terms of the GNU General
@@ -1979,24 +1974,7 @@ Install the rpm. Any error messages?
-
-
- Test reports
-
-Please submit test reports only with the test form
-at sourceforge. Three simple steps:
-
-
- Select category: the distribution you test on.
- Select group: the version of Privoxy that we are about to release.
- Fill the Summary and Detailed Description with something
- intelligent (keep it short and precise).
-
-
- Do not mail to the mailing list (we cannot keep track on issues there).
-
-
-
+
@@ -2429,7 +2407,7 @@ at sourceforge. Three simple steps:
be reset to one if this is the first RPM for
dist which is built from version
X.Y.Z. Check the
- file
+ file
list if unsure. Else, it must be set to the highest already available RPM
release number for that version plus one.
@@ -2563,9 +2541,9 @@ at sourceforge. Three simple steps:
Windows
- You should ensure you have the latest version of Cygwin (from
- http://www.cygwin.com/).
- Run the following commands from within a Cygwin bash shell.
+ Use the
+ Cygwin Time Machine to install the last 1.5 version of Cygwin.
+ Run the following commands from within the Cygwin 1.5 bash shell.
First, make sure that you have freshly exported the right
@@ -2736,114 +2714,10 @@ at sourceforge. Three simple steps:
FreeBSD
- Login to Sourceforge's compile-farm via ssh:
-
-
-
- ssh cf.sourceforge.net
-
-
-
- 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:
-
-
-
- cd current
- autoheader && autoconf && ./configure
-
-
-
- Then run:
-
-
-
- gmake freebsd-dist
-
-
-
- which creates a gzip'ed tar archive. Sadly, you cannot use make
- freebsd-upload on the Sourceforge machine (no ncftpput). You now have
- to manually upload the archive to Sourceforge's ftp server and release
- the file publicly. Use the release notes and Change Log from the
- source tarball package.
-
-
-
- HP-UX 11
-
- First, make sure that you have freshly exported the right
- version into an empty directory. (See "Building and releasing
- packages" above). Then run:
-
-
-
- cd current
- autoheader && autoconf && ./configure
-
-
-
- Then do FIXME.
-
-
-
- Amiga OS
-
- First, make sure that you have freshly exported the right
- version into an empty directory. (See "Building and releasing
- packages" above). Then run:
-
-
-
- cd current
- autoheader && autoconf && ./configure
-
-
-
- Then do FIXME.
-
-
-
- AIX
-
- Login to Sourceforge's compilefarm via ssh:
-
-
-
- ssh cf.sourceforge.net
-
-
-
- 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:
-
-
-
- cd current
- autoheader && autoconf && ./configure
-
-
-
- Then run:
-
-
-
- make aix-dist
-
-
-
- which creates a gzip'ed tar archive. Sadly, you cannot use make
- aix-upload on the Sourceforge machine (no ncftpput). You now have
- to manually upload the archive to Sourceforge's ftp server and release
- the file publicly. Use the release notes and Change Log from the
- source tarball package.
+ Update the www/privoxy port and submit a diff upstream.
+ For details see the FreeBSD Porter's Handbook.
-
Uploading and Releasing Your Package
@@ -2907,10 +2781,10 @@ at sourceforge. Three simple steps:
After the Release
When all (or: most of the) packages have been uploaded and made available,
- send an email to the announce
+ send an email to the announce
mailing list, Subject: "Version X.Y.Z available for download". Be sure to
include the
- download
+ download
location, the release notes and the Changelog. Also, post an
updated News item on the project page Sourceforge, and update the Home
page and docs linked from the Home page (see below). Other news sites
@@ -2965,7 +2839,7 @@ at sourceforge. Three simple steps:
- This will do the upload to the
+ This will do the upload to the
webserver (www.privoxy.org) and ensure all files and directories
there are group writable.