X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fdeveloper-manual.sgml;h=e17e675cb9f781eaae8e6c1c3a27b38551253c15;hb=8566fa5928990558ee7fb10b2fb662ac3d20fb90;hp=bf092366828728628919c1d0cdfdd524f3d3aa06;hpb=b8c19d3bbb2a77892e060d34c1625baf22045dc3;p=privoxy.git diff --git a/doc/source/developer-manual.sgml b/doc/source/developer-manual.sgml index bf092366..e17e675c 100644 --- a/doc/source/developer-manual.sgml +++ b/doc/source/developer-manual.sgml @@ -5,10 +5,10 @@ - - - - + + + + @@ -19,7 +19,7 @@ Purpose : developer manual - Copyright (C) 2001-2021 Privoxy Developers https://www.privoxy.org/ + Copyright (C) 2001-2023 Privoxy Developers https://www.privoxy.org/ See LICENSE. ======================================================================== @@ -39,7 +39,7 @@ Copyright - &my-copy; 2001-2021 by + &my-copy; 2001-2023 by Privoxy Developers @@ -2602,8 +2602,8 @@ make tarball-dist Check that you have the current versions of the NSIS installer, - PCRE library, - MBED TLS library, + PCRE library, + MBED TLS library, Brotli library, and that the MAKENSIS evar in @@ -2813,107 +2813,32 @@ git clean -fd - Mac OS X + macOS / OS X 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 backups 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 can generate 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: - - OSXPackageBuilder module (Documentation out of date) - - 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. - - - - osxsetup module (DEPRECATED) (Documentation out of date) - - 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: - - -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. - - - 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. - - - - macsetup module (Documentation out of date) - - 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 + +git clone ssh://git@git.privoxy.org:23/git/OSXPackageBuilder.git - - - 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. - - + + 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 which version of OS X. + FreeBSD @@ -2952,6 +2877,31 @@ cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co macse + + Updating the RSS feed + + Once the packages are uploaded to SourceForge they should be + mirrored on the Privoxy websites + (https://www.privoxy.org/ + and + http://l3tczdiiwoo63iwxty4lhs6p7eaxop5micbn7vbliydgv63x5zrrrfyd.onion/). + This is usually done by Fabian who uses a couple of shell functions + for this that aren't documented or published yet. + + + Once the packages are uploaded to the mirror the RSS feed has to + be regenerated with a command like: + + + fk@t520 ~/git/privoxy $utils/create-package-feed.pl /tank/backups/sourceforge/frs/project/ijbswa/ doc/webserver/feeds/privoxy-releases.xm + + + The updated RSS feed then has to be uploaded to the SourceForge webserver + and mirrored on the Privoxy websites again. This, too, is usually done + by Fabian with undocumented and unpublished shell functions. + + + After the Release