X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fdeveloper-manual.sgml;h=bede0f141552b8b8cba7b28acda2e1b5dbe10710;hp=2820f445d6946e2132ada679dc0401521c6a0a34;hb=c69d5ea9f898a4e78c7c6efee2ace772bcdce5c9;hpb=5a73e418fa170b0362734c9da5f4921cd413e5f5 diff --git a/doc/source/developer-manual.sgml b/doc/source/developer-manual.sgml index 2820f445..bede0f14 100644 --- a/doc/source/developer-manual.sgml +++ b/doc/source/developer-manual.sgml @@ -21,7 +21,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: developer-manual.sgml,v 1.35 2002/04/17 15:16:15 oes Exp $ + $Id: developer-manual.sgml,v 1.37 2002/04/26 17:23:29 swa Exp $ Written by and Copyright (C) 2001 the SourceForge Privoxy team. http://www.privoxy.org/ @@ -44,7 +44,7 @@ Privoxy Developer Manual - $Id: developer-manual.sgml,v 1.35 2002/04/17 15:16:15 oes Exp $ + $Id: developer-manual.sgml,v 1.37 2002/04/26 17:23:29 swa Exp $ @@ -1720,7 +1720,7 @@ static void unload_re_filterfile( void *f ) { ... } Example for file comments: -const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.35 2002/04/17 15:16:15 oes Exp $"; +const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.37 2002/04/26 17:23:29 swa Exp $"; /********************************************************************* * * File : $Source$ @@ -1780,7 +1780,7 @@ const char FILENAME_h_rcs[] = FILENAME_H_VERSION; #ifndef _FILENAME_H #define _FILENAME_H -#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.35 2002/04/17 15:16:15 oes Exp $" +#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.37 2002/04/26 17:23:29 swa Exp $" /********************************************************************* * * File : $Source$ @@ -1986,7 +1986,7 @@ at sourceforge. Three simple steps: {+add-header{X-Actions-File-Version: A.B} -filter -no-popups} - + Then change the version info in doc/webserver/actions/index.php, @@ -2035,7 +2035,7 @@ at sourceforge. Three simple steps: cd dist cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current - + @@ -2060,7 +2060,7 @@ at sourceforge. Three simple steps: cd current autoheader && autoconf && ./configure - + Then do: @@ -2068,7 +2068,7 @@ at sourceforge. Three simple steps: make tarball-dist - + To upload the package to Sourceforge, simply issue @@ -2076,7 +2076,7 @@ at sourceforge. Three simple steps: make tarball-upload - + Go to the displayed URL and release the file publicly on Sourceforge. @@ -2095,7 +2095,7 @@ at sourceforge. Three simple steps: cd current autoheader && autoconf && ./configure - + Then do @@ -2103,7 +2103,7 @@ at sourceforge. Three simple steps: make suse-dist (or make redhat-dist) - + To upload the package to Sourceforge, simply issue @@ -2111,7 +2111,7 @@ at sourceforge. Three simple steps: make suse-upload (or make redhat-upload) - + Go to the displayed URL and release the file publicly on Sourceforge. @@ -2128,7 +2128,7 @@ at sourceforge. Three simple steps: cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setup - + You will need a mix of development tools. @@ -2148,7 +2148,7 @@ at sourceforge. Three simple steps: installExeName='privoxyos2_setup_X.Y.Z.exe' - + Next, edit the IJB.wis file so the release number matches @@ -2157,7 +2157,7 @@ at sourceforge. Three simple steps: PACKAGEID="Privoxy Team\Privoxy\Privoxy Package\X\Y\Z" - + You're now ready to build. Run: @@ -2165,7 +2165,7 @@ at sourceforge. Three simple steps: os2build - + You will find the WarpIN-installable executable in the @@ -2183,7 +2183,7 @@ at sourceforge. Three simple steps: ssh cf.sourceforge.net - + Choose the right operating system (not the Debian one). @@ -2195,7 +2195,7 @@ at sourceforge. Three simple steps: cd current autoheader && autoconf && ./configure - + Then run @@ -2203,7 +2203,7 @@ at sourceforge. Three simple steps: gmake solaris-dist - + which creates a gzip'ed tar archive. Sadly, you cannot use make @@ -2228,7 +2228,7 @@ at sourceforge. Three simple steps: cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co winsetup - + Then you can build the package. This is fully automated, and is @@ -2239,7 +2239,7 @@ at sourceforge. Three simple steps: cd winsetup make - + Now you can manually rename privoxy_setup.exe to @@ -2259,7 +2259,7 @@ at sourceforge. Three simple steps: cd current autoheader && autoconf && ./configure - + Then do FIXME. @@ -2275,7 +2275,7 @@ at sourceforge. Three simple steps: cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co osxsetup - + Then run: @@ -2284,7 +2284,7 @@ at sourceforge. Three simple steps: cd osxsetup build - + This will run autoheader, autoconf and @@ -2301,7 +2301,7 @@ at sourceforge. Three simple steps: zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg - + You can then upload privoxyosx_setup_x.y.z.zip anonymously to @@ -2318,7 +2318,7 @@ zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg ssh cf.sourceforge.net - + Choose the right operating system. @@ -2330,7 +2330,7 @@ zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg cd current autoheader && autoconf && ./configure - + Then run: @@ -2338,7 +2338,7 @@ zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg gmake freebsd-dist - + which creates a gzip'ed tar archive. Sadly, you cannot use make @@ -2359,7 +2359,7 @@ zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg cd current autoheader && autoconf && ./configure - + Then do FIXME. @@ -2376,7 +2376,7 @@ zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg cd current autoheader && autoconf && ./configure - + Then do FIXME. @@ -2390,7 +2390,7 @@ zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg ssh cf.sourceforge.net - + Choose the right operating system. @@ -2402,7 +2402,7 @@ zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg cd current autoheader && autoconf && ./configure - + Then run: @@ -2410,7 +2410,7 @@ zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg make aix-dist - + which creates a gzip'ed tar archive. Sadly, you cannot use make @@ -2422,6 +2422,59 @@ zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg + + Uploading and Releasing Your Package + + After the package is ready, it is time to upload it + to SourceForge, and go through the release steps. The upload + is done via FTP: + + + + + + Upload to: ftp://upload.sourceforge.net/incoming + + + + + user: anonymous + + + + + password: ijbswa-developers@lists.sourceforge.net + + + + + + Once this done go to http://sourceforge.net/project/admin/editpackages.php?group_id=11118, + making sure you are logged in. Find your target platform in the + second 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. &p-version; + (beta). + + + Now just follow the prompts. Be sure to add any appropriate Release + notes. You should see your freshly uploaded packages in + Step 2. Add Files To This Release. Check the + appropriate box(es). Remember at each step to hit the + Refresh/Submit buttons! You should now see your + file(s) listed in Step 3. Fill out the forms with the appropriate + information for your platform, being sure to hit Update + for each file. If anyone is monitoring your platform, check the + email box at the very bottom to notify them of + the new package. This should do it! + + + If you have made errors, or need to make changes, you can go through + essentially the same steps, but select Edit Release, + instead of Add Release. + + + After the Release @@ -2450,7 +2503,7 @@ zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg make dok # (or make redkat-dok if make dok doesn't work for you) - + That will generate doc/webserver/user-manual, @@ -2476,7 +2529,7 @@ zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg make webserver - + This will do the upload to the @@ -2542,6 +2595,12 @@ zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg Temple Place - Suite 330, Boston, MA 02111-1307, USA. $Log: developer-manual.sgml,v $ + Revision 1.37 2002/04/26 17:23:29 swa + bookmarks cleaned, changed structure of user manual, screen and programlisting cleanups, and numerous other changes that I forgot + + Revision 1.36 2002/04/26 05:25:23 hal9 + Mass commit to catch a few scattered fixes. + Revision 1.35 2002/04/17 15:16:15 oes Added link to docbook crash course