X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;ds=inline;f=doc%2Fwebserver%2Fdeveloper-manual%2Fnewrelease.html;h=91944096b7c87fffa3c159a1f0e01be97a3d897b;hb=7a99a61ab1a3ce0401821aedcd06eba19a698b2a;hp=8597fbe0f97cd7565d219f2585e3135fb0aef0d4;hpb=23be303a582b85ccac7592d0135f0beb9cf170f6;p=privoxy.git diff --git a/doc/webserver/developer-manual/newrelease.html b/doc/webserver/developer-manual/newrelease.html index 8597fbe0..91944096 100644 --- a/doc/webserver/developer-manual/newrelease.html +++ b/doc/webserver/developer-manual/newrelease.html @@ -185,11 +185,11 @@ Finished docs should be then be committed to CVS (for those without the ability to build these). Some docs may require rather obscure processing tools. config, the man page - (and the html version of the man page), and the PDF docs fall in - this category. REAMDE, the man page, AUTHORS, and config should all - also be committed to CVS for other packagers. The formal docs - should be uploaded to the webserver. See the Section "Updating the - webserver" in this manual for details.

+ (and the html version of the man page) fall in this category. + REAMDE, the man page, AUTHORS, and config should all also be + committed to CVS for other packagers. The formal docs should be + uploaded to the webserver. See the Section "Updating the webserver" + in this manual for details.

  • @@ -682,10 +682,11 @@

    6.3.6. 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 version into an empty @@ -738,7 +739,7 @@ 

    -  debchange -v 3.0.20-UNRELEASED-1 "New upstream version"
+  debchange -v 3.0.25-UNRELEASED-1 "New upstream version"
    @@ -757,7 +758,7 @@

    This will create ../privoxy_3.0.20-UNRELEASED-1_i386.deb which can be + "FILENAME">../privoxy_3.0.25-UNRELEASED-1_i386.deb which can be uploaded. To upload the package to Sourceforge, simply issue

    @@ -911,148 +912,10 @@

    6.3.9. 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.

    - - -
    -

    6.3.10. 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.

    -
    - -
    -

    6.3.11. 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.

    -
    - -
    -

    6.3.12. 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.

    @@ -1090,7 +953,7 @@ 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.20 (beta).

    + "emphasis">3.0.25 (beta).

    Now just follow the prompts. Be sure to add any appropriate Release notes. You should see your freshly uploaded packages in