doc/webserver/developer-manual/newrelease.html

   1 <HTML
   2 ><HEAD
   3 ><TITLE
   4 >Releasing a new version</TITLE
   5 ><META
   6 NAME="GENERATOR"
   7 CONTENT="Modular DocBook HTML Stylesheet Version 1.64
   8 "><LINK
   9 REL="HOME"
  10 TITLE="Privoxy Developer Manual"
  11 HREF="index.html"><LINK
  12 REL="PREVIOUS"
  13 TITLE="Testing Guidelines"
  14 HREF="testing.html"><LINK
  15 REL="NEXT"
  16 TITLE="Contacting the developers, Bug Reporting and Feature Requests"
  17 HREF="contact.html"><LINK
  18 REL="STYLESHEET"
  19 TYPE="text/css"
  20 HREF="../p_doc.css"></HEAD
  21 ><BODY
  22 CLASS="SECT1"
  23 BGCOLOR="#EEEEEE"
  24 TEXT="#000000"
  25 LINK="#0000FF"
  26 VLINK="#840084"
  27 ALINK="#0000FF"
  28 ><DIV
  29 CLASS="NAVHEADER"
  30 ><TABLE
  31 WIDTH="100%"
  32 BORDER="0"
  33 CELLPADDING="0"
  34 CELLSPACING="0"
  35 ><TR
  36 ><TH
  37 COLSPAN="3"
  38 ALIGN="center"
  39 >Privoxy Developer Manual</TH
  40 ></TR
  41 ><TR
  42 ><TD
  43 WIDTH="10%"
  44 ALIGN="left"
  45 VALIGN="bottom"
  46 ><A
  47 HREF="testing.html"
  48 >Prev</A
  49 ></TD
  50 ><TD
  51 WIDTH="80%"
  52 ALIGN="center"
  53 VALIGN="bottom"
  54 ></TD
  55 ><TD
  56 WIDTH="10%"
  57 ALIGN="right"
  58 VALIGN="bottom"
  59 ><A
  60 HREF="contact.html"
  61 >Next</A
  62 ></TD
  63 ></TR
  64 ></TABLE
  65 ><HR
  66 ALIGN="LEFT"
  67 WIDTH="100%"></DIV
  68 ><DIV
  69 CLASS="SECT1"
  70 ><H1
  71 CLASS="SECT1"
  72 ><A
  73 NAME="NEWRELEASE"
  74 >8. Releasing a new version</A
  75 ></H1
  76 ><P
  77 >       To minimize trouble with distribution contents, webpage
  78         errors and the like, we strongly encourage you
  79         to follow this section if you prepare a new release of
  80         code or new pages on the webserver.
  81     </P
  82 ><P
  83 >       The following programs are required to follow this process:
  84         <TT
  85 CLASS="FILENAME"
  86 >ncftpput</TT
  87 > (ncftp), <TT
  88 CLASS="FILENAME"
  89 >scp</TT
  90 > (ssh),
  91 <TT
  92 CLASS="FILENAME"
  93 >gmake</TT
  94 > (GNU's version of make), autoconf, cvs, ???.
  95     </P
  96 ><DIV
  97 CLASS="SECT2"
  98 ><H2
  99 CLASS="SECT2"
 100 ><A
 101 NAME="BEFORERELEASE"
 102 >8.1. Before the Release</A
 103 ></H2
 104 ><P
 105 >       The following <I
 106 CLASS="EMPHASIS"
 107 >must be done by one of the
 108        developers</I
 109 > prior to each new release:
 110      </P
 111 ><P
 112 >      <P
 113 ></P
 114 ><UL
 115 ><LI
 116 ><P
 117 >         Make sure that everybody who has worked on the code in the last
 118          couple of days has had a chance to yell <SPAN
 119 CLASS="QUOTE"
 120 >"no!"</SPAN
 121 > in case
 122          they have pending changes/fixes in their pipelines.
 123         </P
 124 ></LI
 125 ><LI
 126 ><P
 127 >         Increment the version number in <TT
 128 CLASS="FILENAME"
 129 >configure.in</TT
 130 > in
 131          CVS. Also, the RPM release number in
 132          <TT
 133 CLASS="FILENAME"
 134 >configure.in</TT
 135 >. Do NOT touch version information
 136          after export from CVS. <I
 137 CLASS="EMPHASIS"
 138 >All packages</I
 139 > will use the
 140          version and release data from <TT
 141 CLASS="FILENAME"
 142 >configure.in</TT
 143 >.
 144          Local files should not be changed, except prior to a CVS commit!!!
 145          This way we are all on the same page!
 146        </P
 147 ></LI
 148 ><LI
 149 ><P
 150 >        If the default actionsfile has changed since last release,
 151         bump up its version info in this line:
 152        </P
 153 ><P
 154 >
 155         <TABLE
 156 BORDER="0"
 157 BGCOLOR="#E0E0E0"
 158 WIDTH="90%"
 159 ><TR
 160 ><TD
 161 ><PRE
 162 CLASS="PROGRAMLISTING"
 163 >  {+add-header{X-Actions-File-Version: A.B} -filter -no-popups}
 164         </PRE
 165 ></TD
 166 ></TR
 167 ></TABLE
 168 >
 169        </P
 170 ><P
 171 >
 172         Then change the version info in doc/webserver/actions/index.php,
 173         line: '$required_actions_file_version = "A.B";'
 174        </P
 175 ></LI
 176 ><LI
 177 ><P
 178 >        Tag all files in CVS with the version number with
 179         <SPAN
 180 CLASS="QUOTE"
 181 >"<B
 182 CLASS="COMMAND"
 183 >cvs tag v_X_Y_Z</B
 184 >"</SPAN
 185 > (where X = major, Y
 186         = minor, Z = point). Don't use vX_Y_Z, ver_X_Y_Z, v_X.Y.Z (won't work)
 187         etc.
 188        </P
 189 ></LI
 190 ><LI
 191 ><P
 192 >        The first package uploaded should be the official
 193         <SPAN
 194 CLASS="QUOTE"
 195 >"tarball"</SPAN
 196 > release. This is built with the
 197         <SPAN
 198 CLASS="QUOTE"
 199 >"<B
 200 CLASS="COMMAND"
 201 >make tarball-dist</B
 202 >"</SPAN
 203 > Makefile
 204         target, and then can be uploaded with
 205         <SPAN
 206 CLASS="QUOTE"
 207 >"<B
 208 CLASS="COMMAND"
 209 >make tarball-upload</B
 210 >"</SPAN
 211 > (see below).
 212        </P
 213 ></LI
 214 ></UL
 215 >
 216      </P
 217 ></DIV
 218 ><DIV
 219 CLASS="SECT2"
 220 ><H2
 221 CLASS="SECT2"
 222 ><A
 223 NAME="NEWRELEASE-WEB"
 224 >8.2. Update the webserver</A
 225 ></H2
 226 ><P
 227 >       All files must be group-readable and group-writable (or no one else
 228         will be able to change them). To update the webserver, create any
 229         pages locally in the <TT
 230 CLASS="FILENAME"
 231 >doc/webserver</TT
 232 > directory (or
 233         create new directories under <TT
 234 CLASS="FILENAME"
 235 >doc/webserver</TT
 236 >), then do
 237         </P
 238 ><P
 239 >       <TABLE
 240 BORDER="0"
 241 BGCOLOR="#E0E0E0"
 242 WIDTH="100%"
 243 ><TR
 244 ><TD
 245 ><PRE
 246 CLASS="PROGRAMLISTING"
 247 >  make webserver
 248         </PRE
 249 ></TD
 250 ></TR
 251 ></TABLE
 252 >
 253         </P
 254 ><P
 255 >       Note that <SPAN
 256 CLASS="QUOTE"
 257 >"<B
 258 CLASS="COMMAND"
 259 >make dok</B
 260 >"</SPAN
 261 >
 262      (or <SPAN
 263 CLASS="QUOTE"
 264 >"<B
 265 CLASS="COMMAND"
 266 >make redhat-dok</B
 267 >"</SPAN
 268 >) creates
 269         <TT
 270 CLASS="FILENAME"
 271 >doc/webserver/user-manual</TT
 272 >,
 273         <TT
 274 CLASS="FILENAME"
 275 >doc/webserver/developer-manual</TT
 276 >,
 277         <TT
 278 CLASS="FILENAME"
 279 >doc/webserver/faq</TT
 280 > and
 281         <TT
 282 CLASS="FILENAME"
 283 >doc/webserver/man-page</TT
 284 > automatically.
 285       </P
 286 ><P
 287 >      Please do NOT use any other means of transferring files to the
 288       webserver. <SPAN
 289 CLASS="QUOTE"
 290 >"<B
 291 CLASS="COMMAND"
 292 >make webserver</B
 293 >"</SPAN
 294 > not only
 295       uploads, but will make sure that the appropriate permissions are
 296       preserved for shared group access.
 297       </P
 298 ></DIV
 299 ><DIV
 300 CLASS="SECT2"
 301 ><H2
 302 CLASS="SECT2"
 303 ><A
 304 NAME="NEWRELEASE-RPM"
 305 >8.3. SuSE or Red Hat</A
 306 ></H2
 307 ><P
 308 >       Ensure that you have the latest code version. Hence run:
 309         </P
 310 ><P
 311 >       <TABLE
 312 BORDER="0"
 313 BGCOLOR="#E0E0E0"
 314 WIDTH="100%"
 315 ><TR
 316 ><TD
 317 ><PRE
 318 CLASS="PROGRAMLISTING"
 319 >  cd current
 320   cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
 321   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
 322         </PRE
 323 ></TD
 324 ></TR
 325 ></TABLE
 326 >
 327         </P
 328 ><P
 329 >        first.
 330         </P
 331 ><P
 332 >       <TABLE
 333 BORDER="0"
 334 BGCOLOR="#E0E0E0"
 335 WIDTH="100%"
 336 ><TR
 337 ><TD
 338 ><PRE
 339 CLASS="PROGRAMLISTING"
 340 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
 341         </PRE
 342 ></TD
 343 ></TR
 344 ></TABLE
 345 >
 346         </P
 347 ><P
 348 >       Then do
 349         </P
 350 ><P
 351 >       <TABLE
 352 BORDER="0"
 353 BGCOLOR="#E0E0E0"
 354 WIDTH="100%"
 355 ><TR
 356 ><TD
 357 ><PRE
 358 CLASS="PROGRAMLISTING"
 359 >  make suse-dist or make redhat-dist
 360         </PRE
 361 ></TD
 362 ></TR
 363 ></TABLE
 364 >
 365         </P
 366 ><P
 367 >       To upload the package to Sourceforge, simply issue
 368         </P
 369 ><P
 370 >       <TABLE
 371 BORDER="0"
 372 BGCOLOR="#E0E0E0"
 373 WIDTH="100%"
 374 ><TR
 375 ><TD
 376 ><PRE
 377 CLASS="PROGRAMLISTING"
 378 >  make suse-upload or make redhat-upload
 379         </PRE
 380 ></TD
 381 ></TR
 382 ></TABLE
 383 >
 384         </P
 385 ><P
 386 >       Go to the displayed URL and release the file publicly on Sourceforge.
 387       </P
 388 ></DIV
 389 ><DIV
 390 CLASS="SECT2"
 391 ><H2
 392 CLASS="SECT2"
 393 ><A
 394 NAME="NEWRELEASE-OS2"
 395 >8.4. OS/2</A
 396 ></H2
 397 ><P
 398 >       Ensure that you have the latest code version. Hence run:
 399         </P
 400 ><P
 401 >       <TABLE
 402 BORDER="0"
 403 BGCOLOR="#E0E0E0"
 404 WIDTH="100%"
 405 ><TR
 406 ><TD
 407 ><PRE
 408 CLASS="PROGRAMLISTING"
 409 >  cd current
 410   cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
 411   cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
 412   cd ..
 413   cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setup
 414         </PRE
 415 ></TD
 416 ></TR
 417 ></TABLE
 418 >
 419         </P
 420 ><P
 421 >       You will need a mix of development tools.
 422         The main compilation takes place with IBM Visual Age C++.
 423         Some ancillary work takes place with GNU tools, available from
 424         various sources like hobbes.nmsu.edu.
 425         Specificially, you will need <TT
 426 CLASS="FILENAME"
 427 >autoheader</TT
 428 >,
 429         <TT
 430 CLASS="FILENAME"
 431 >autoconf</TT
 432 > and <TT
 433 CLASS="FILENAME"
 434 >sh</TT
 435 > tools.
 436         The packaging takes place with WarpIN, available from various sources, including
 437         its home page: <A
 438 HREF="http://www.xworkplace.org/"
 439 TARGET="_top"
 440 >xworkplace</A
 441 >.
 442         </P
 443 ><P
 444 >       Change directory to the <TT
 445 CLASS="FILENAME"
 446 >os2setup</TT
 447 > directory.
 448         Edit the os2build.cmd file to set the final executable filename.
 449         For example,
 450         <TABLE
 451 BORDER="0"
 452 BGCOLOR="#E0E0E0"
 453 WIDTH="100%"
 454 ><TR
 455 ><TD
 456 ><PRE
 457 CLASS="PROGRAMLISTING"
 458 >  installExeName='privoxyos2_setup_X.Y.Z.exe'
 459         </PRE
 460 ></TD
 461 ></TR
 462 ></TABLE
 463 >
 464         Next, edit the <TT
 465 CLASS="FILENAME"
 466 >IJB.wis</TT
 467 > file so the release number matches
 468         in the <TT
 469 CLASS="FILENAME"
 470 >PACKAGEID</TT
 471 > section:
 472         <TABLE
 473 BORDER="0"
 474 BGCOLOR="#E0E0E0"
 475 WIDTH="100%"
 476 ><TR
 477 ><TD
 478 ><PRE
 479 CLASS="PROGRAMLISTING"
 480 >  PACKAGEID="Privoxy Team\Privoxy\Privoxy Package\X\Y\Z"
 481         </PRE
 482 ></TD
 483 ></TR
 484 ></TABLE
 485 >
 486         You're now ready to build.  Run:
 487         <TABLE
 488 BORDER="0"
 489 BGCOLOR="#E0E0E0"
 490 WIDTH="100%"
 491 ><TR
 492 ><TD
 493 ><PRE
 494 CLASS="PROGRAMLISTING"
 495 >  os2build
 496         </PRE
 497 ></TD
 498 ></TR
 499 ></TABLE
 500 >
 501      And in the <TT
 502 CLASS="FILENAME"
 503 >./files</TT
 504 > directory you will have the
 505      WarpIN-installable executable.
 506      Upload this anonymously to
 507      <TT
 508 CLASS="FILENAME"
 509 >uploads.sourceforge.net/incoming</TT
 510 >, create a release
 511      for it, and you're done.
 512         </P
 513 ></DIV
 514 ><DIV
 515 CLASS="SECT2"
 516 ><H2
 517 CLASS="SECT2"
 518 ><A
 519 NAME="NEWRELEASE-SOLARIS"
 520 >8.5. Solaris</A
 521 ></H2
 522 ><P
 523 >       Login to Sourceforge's compilefarm via ssh
 524         </P
 525 ><P
 526 >       <TABLE
 527 BORDER="0"
 528 BGCOLOR="#E0E0E0"
 529 WIDTH="100%"
 530 ><TR
 531 ><TD
 532 ><PRE
 533 CLASS="PROGRAMLISTING"
 534 >  ssh cf.sourceforge.net
 535         </PRE
 536 ></TD
 537 ></TR
 538 ></TABLE
 539 >
 540         </P
 541 ><P
 542 >       Choose the right operating system (not the Debian one). If you have
 543         downloaded <SPAN
 544 CLASS="APPLICATION"
 545 >Privoxy</SPAN
 546 > before,
 547         </P
 548 ><P
 549 >       <TABLE
 550 BORDER="0"
 551 BGCOLOR="#E0E0E0"
 552 WIDTH="100%"
 553 ><TR
 554 ><TD
 555 ><PRE
 556 CLASS="PROGRAMLISTING"
 557 >  cd current
 558   cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
 559   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
 560         </PRE
 561 ></TD
 562 ></TR
 563 ></TABLE
 564 >
 565         </P
 566 ><P
 567 >       If not, please <A
 568 HREF="http://www.privoxy.org/user-manual/user-manual/installation.html#INSTALLATION-SOURCE"
 569 TARGET="_top"
 570 >checkout
 571         Privoxy via CVS first</A
 572 >. Run:
 573         </P
 574 ><P
 575 >       <TABLE
 576 BORDER="0"
 577 BGCOLOR="#E0E0E0"
 578 WIDTH="100%"
 579 ><TR
 580 ><TD
 581 ><PRE
 582 CLASS="PROGRAMLISTING"
 583 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
 584         </PRE
 585 ></TD
 586 ></TR
 587 ></TABLE
 588 >
 589         </P
 590 ><P
 591 >       Then run
 592         </P
 593 ><P
 594 >       <TABLE
 595 BORDER="0"
 596 BGCOLOR="#E0E0E0"
 597 WIDTH="100%"
 598 ><TR
 599 ><TD
 600 ><PRE
 601 CLASS="PROGRAMLISTING"
 602 >  gmake solaris-dist
 603         </PRE
 604 ></TD
 605 ></TR
 606 ></TABLE
 607 >
 608         </P
 609 ><P
 610 >       which creates a gzip'ed tar archive. Sadly, you cannot use <B
 611 CLASS="COMMAND"
 612 >make
 613         solaris-upload</B
 614 > on the Sourceforge machine (no ncftpput). You now have
 615         to manually upload the archive to Sourceforge's ftp server and release
 616         the file publicly.
 617         </P
 618 ></DIV
 619 ><DIV
 620 CLASS="SECT2"
 621 ><H2
 622 CLASS="SECT2"
 623 ><A
 624 NAME="NEWRELEASE-WINDOWS"
 625 >8.6. Windows</A
 626 ></H2
 627 ><P
 628 >       Ensure that you have the latest code version. Hence run
 629         </P
 630 ><P
 631 >       <TABLE
 632 BORDER="0"
 633 BGCOLOR="#E0E0E0"
 634 WIDTH="100%"
 635 ><TR
 636 ><TD
 637 ><PRE
 638 CLASS="PROGRAMLISTING"
 639 >  cd current
 640   cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
 641   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
 642         </PRE
 643 ></TD
 644 ></TR
 645 ></TABLE
 646 >
 647         </P
 648 ><P
 649 >        Run:
 650         </P
 651 ><P
 652 >       <TABLE
 653 BORDER="0"
 654 BGCOLOR="#E0E0E0"
 655 WIDTH="100%"
 656 ><TR
 657 ><TD
 658 ><PRE
 659 CLASS="PROGRAMLISTING"
 660 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
 661         </PRE
 662 ></TD
 663 ></TR
 664 ></TABLE
 665 >
 666         </P
 667 ><P
 668 >       Then do FIXME.
 669         </P
 670 ></DIV
 671 ><DIV
 672 CLASS="SECT2"
 673 ><H2
 674 CLASS="SECT2"
 675 ><A
 676 NAME="NEWRELEASE-DEBIAN"
 677 >8.7. Debian</A
 678 ></H2
 679 ><P
 680 >       Ensure that you have the latest code version. Hence run:
 681         </P
 682 ><P
 683 >       <TABLE
 684 BORDER="0"
 685 BGCOLOR="#E0E0E0"
 686 WIDTH="100%"
 687 ><TR
 688 ><TD
 689 ><PRE
 690 CLASS="PROGRAMLISTING"
 691 >  cd current
 692   cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
 693   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
 694         </PRE
 695 ></TD
 696 ></TR
 697 ></TABLE
 698 >
 699         </P
 700 ><P
 701 >       first. Run:
 702         </P
 703 ><P
 704 >       <TABLE
 705 BORDER="0"
 706 BGCOLOR="#E0E0E0"
 707 WIDTH="100%"
 708 ><TR
 709 ><TD
 710 ><PRE
 711 CLASS="PROGRAMLISTING"
 712 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
 713         </PRE
 714 ></TD
 715 ></TR
 716 ></TABLE
 717 >
 718         </P
 719 ><P
 720 >       Then do FIXME.
 721         </P
 722 ></DIV
 723 ><DIV
 724 CLASS="SECT2"
 725 ><H2
 726 CLASS="SECT2"
 727 ><A
 728 NAME="NEWRELEASE-MACOSX"
 729 >8.8. Mac OSX</A
 730 ></H2
 731 ><P
 732 >       Ensure that you have the latest code version. Hence run:
 733         </P
 734 ><P
 735 >       <TABLE
 736 BORDER="0"
 737 BGCOLOR="#E0E0E0"
 738 WIDTH="100%"
 739 ><TR
 740 ><TD
 741 ><PRE
 742 CLASS="PROGRAMLISTING"
 743 >  cd current
 744   cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
 745   cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
 746   cd ..
 747   cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co osxsetup
 748         </PRE
 749 ></TD
 750 ></TR
 751 ></TABLE
 752 >
 753         </P
 754 ><P
 755 >       From the osxsetup directory, run:
 756         <TABLE
 757 BORDER="0"
 758 BGCOLOR="#E0E0E0"
 759 WIDTH="100%"
 760 ><TR
 761 ><TD
 762 ><PRE
 763 CLASS="PROGRAMLISTING"
 764 >  build
 765         </PRE
 766 ></TD
 767 ></TR
 768 ></TABLE
 769 >
 770         </P
 771 ><P
 772 >       This will run <TT
 773 CLASS="FILENAME"
 774 >autoheader</TT
 775 >, <TT
 776 CLASS="FILENAME"
 777 >autoconf</TT
 778 > and
 779         <TT
 780 CLASS="FILENAME"
 781 >configure</TT
 782 > as well as <TT
 783 CLASS="FILENAME"
 784 >make</TT
 785 >.
 786         Finally, it will copy over the necessary files to the ./osxsetup/files directory
 787         for further processing by <TT
 788 CLASS="FILENAME"
 789 >PackageMaker</TT
 790 >.
 791         </P
 792 ><P
 793 >       Bring up PackageMaker with the PrivoxyPackage.pmsp definition file, modify the package
 794         name to match the release, and hit the "Create package" button.
 795         If you specify ./Privoxy.pkg as the output package name, you can then create
 796         the distributable zip file with the command:
 797         <TABLE
 798 BORDER="0"
 799 BGCOLOR="#E0E0E0"
 800 WIDTH="100%"
 801 ><TR
 802 ><TD
 803 ><PRE
 804 CLASS="PROGRAMLISTING"
 805 >zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg
 806         </PRE
 807 ></TD
 808 ></TR
 809 ></TABLE
 810 >
 811         You can then upload <TT
 812 CLASS="FILENAME"
 813 >privoxyosx_setup_x.y.z.zip</TT
 814 > anonymously to
 815         <TT
 816 CLASS="FILENAME"
 817 >uploads.sourceforge.net/incoming</TT
 818 >,
 819         create a release for it, and you're done.
 820         </P
 821 ></DIV
 822 ><DIV
 823 CLASS="SECT2"
 824 ><H2
 825 CLASS="SECT2"
 826 ><A
 827 NAME="NEWRELEASE-FREEBSD"
 828 >8.9. FreeBSD</A
 829 ></H2
 830 ><P
 831 >       Change the version number of <SPAN
 832 CLASS="APPLICATION"
 833 >Privoxy</SPAN
 834 > in the
 835         configure.in file. Run:
 836         <TABLE
 837 BORDER="0"
 838 BGCOLOR="#E0E0E0"
 839 WIDTH="100%"
 840 ><TR
 841 ><TD
 842 ><PRE
 843 CLASS="PROGRAMLISTING"
 844 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
 845         </PRE
 846 ></TD
 847 ></TR
 848 ></TABLE
 849 >
 850         Then ...
 851       </P
 852 ><P
 853 >       Login to Sourceforge's compilefarm via ssh:
 854         </P
 855 ><P
 856 >       <TABLE
 857 BORDER="0"
 858 BGCOLOR="#E0E0E0"
 859 WIDTH="100%"
 860 ><TR
 861 ><TD
 862 ><PRE
 863 CLASS="PROGRAMLISTING"
 864 >  ssh cf.sourceforge.net
 865         </PRE
 866 ></TD
 867 ></TR
 868 ></TABLE
 869 >
 870         </P
 871 ><P
 872 >       Choose the right operating system. If you have downloaded Privoxy
 873         before,
 874         </P
 875 ><P
 876 >       <TABLE
 877 BORDER="0"
 878 BGCOLOR="#E0E0E0"
 879 WIDTH="100%"
 880 ><TR
 881 ><TD
 882 ><PRE
 883 CLASS="PROGRAMLISTING"
 884 >  cd current
 885   cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
 886   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
 887         </PRE
 888 ></TD
 889 ></TR
 890 ></TABLE
 891 >
 892         </P
 893 ><P
 894 >       If not, please <A
 895 HREF="http://www.privoxy.org/user-manual/user-manual/installation.html#INSTALLATION-SOURCE"
 896 TARGET="_top"
 897 >checkout
 898         Privoxy via CVS first</A
 899 >. Run:
 900         </P
 901 ><P
 902 >       <TABLE
 903 BORDER="0"
 904 BGCOLOR="#E0E0E0"
 905 WIDTH="100%"
 906 ><TR
 907 ><TD
 908 ><PRE
 909 CLASS="PROGRAMLISTING"
 910 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
 911         </PRE
 912 ></TD
 913 ></TR
 914 ></TABLE
 915 >
 916         </P
 917 ><P
 918 >       Then run:
 919         </P
 920 ><P
 921 >       <TABLE
 922 BORDER="0"
 923 BGCOLOR="#E0E0E0"
 924 WIDTH="100%"
 925 ><TR
 926 ><TD
 927 ><PRE
 928 CLASS="PROGRAMLISTING"
 929 >  gmake freebsd-dist
 930         </PRE
 931 ></TD
 932 ></TR
 933 ></TABLE
 934 >
 935         </P
 936 ><P
 937 >       which creates a gzip'ed tar archive. Sadly, you cannot use <B
 938 CLASS="COMMAND"
 939 >make
 940         freebsd-upload</B
 941 > on the Sourceforge machine (no ncftpput). You now have
 942         to manually upload the archive to Sourceforge's ftp server and release
 943         the file publicly.
 944         </P
 945 ></DIV
 946 ><DIV
 947 CLASS="SECT2"
 948 ><H2
 949 CLASS="SECT2"
 950 ><A
 951 NAME="NEWRELEASE-TARBALL"
 952 >8.10. Tarball</A
 953 ></H2
 954 ><P
 955 >       Ensure that you have the latest code version. Hence run:
 956         </P
 957 ><P
 958 >       <TABLE
 959 BORDER="0"
 960 BGCOLOR="#E0E0E0"
 961 WIDTH="100%"
 962 ><TR
 963 ><TD
 964 ><PRE
 965 CLASS="PROGRAMLISTING"
 966 >  cd current
 967   cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
 968   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
 969         </PRE
 970 ></TD
 971 ></TR
 972 ></TABLE
 973 >
 974         </P
 975 ><P
 976 >       first. Run:
 977         </P
 978 ><P
 979 >       <TABLE
 980 BORDER="0"
 981 BGCOLOR="#E0E0E0"
 982 WIDTH="100%"
 983 ><TR
 984 ><TD
 985 ><PRE
 986 CLASS="PROGRAMLISTING"
 987 >  make clobber
 988   autoheader &#38;&#38; autoconf &#38;&#38; ./configure
 989         </PRE
 990 ></TD
 991 ></TR
 992 ></TABLE
 993 >
 994         </P
 995 ><P
 996 >       Then do:
 997         </P
 998 ><P
 999 >       <TABLE
1000 BORDER="0"
1001 BGCOLOR="#E0E0E0"
1002 WIDTH="100%"
1003 ><TR
1004 ><TD
1005 ><PRE
1006 CLASS="PROGRAMLISTING"
1007 >  make tarball-dist
1008         </PRE
1009 ></TD
1010 ></TR
1011 ></TABLE
1012 >
1013         </P
1014 ><P
1015 >       To upload the package to Sourceforge, simply issue
1016         </P
1017 ><P
1018 >       <TABLE
1019 BORDER="0"
1020 BGCOLOR="#E0E0E0"
1021 WIDTH="100%"
1022 ><TR
1023 ><TD
1024 ><PRE
1025 CLASS="PROGRAMLISTING"
1026 >  make tarball-upload
1027         </PRE
1028 ></TD
1029 ></TR
1030 ></TABLE
1031 >
1032         </P
1033 ><P
1034 >       Goto the displayed URL and release the file publicly on Sourceforge.
1035       </P
1036 ></DIV
1037 ><DIV
1038 CLASS="SECT2"
1039 ><H2
1040 CLASS="SECT2"
1041 ><A
1042 NAME="NEWRELEASE-HPUX"
1043 >8.11. HP-UX 11</A
1044 ></H2
1045 ><P
1046 >       Ensure that you have the latest code version. Hence run:
1047         </P
1048 ><P
1049 >       <TABLE
1050 BORDER="0"
1051 BGCOLOR="#E0E0E0"
1052 WIDTH="100%"
1053 ><TR
1054 ><TD
1055 ><PRE
1056 CLASS="PROGRAMLISTING"
1057 >  cd current
1058   cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1059   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
1060         </PRE
1061 ></TD
1062 ></TR
1063 ></TABLE
1064 >
1065         </P
1066 ><P
1067 >       first. Run:
1068         </P
1069 ><P
1070 >       <TABLE
1071 BORDER="0"
1072 BGCOLOR="#E0E0E0"
1073 WIDTH="100%"
1074 ><TR
1075 ><TD
1076 ><PRE
1077 CLASS="PROGRAMLISTING"
1078 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
1079         </PRE
1080 ></TD
1081 ></TR
1082 ></TABLE
1083 >
1084         </P
1085 ><P
1086 >       Then do FIXME.
1087         </P
1088 ></DIV
1089 ><DIV
1090 CLASS="SECT2"
1091 ><H2
1092 CLASS="SECT2"
1093 ><A
1094 NAME="NEWRELEASE-AMIGA"
1095 >8.12. Amiga OS</A
1096 ></H2
1097 ><P
1098 >       Ensure that you have the latest code version. Hence run:
1099         </P
1100 ><P
1101 >       <TABLE
1102 BORDER="0"
1103 BGCOLOR="#E0E0E0"
1104 WIDTH="100%"
1105 ><TR
1106 ><TD
1107 ><PRE
1108 CLASS="PROGRAMLISTING"
1109 >  cd current
1110   cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1111   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
1112         </PRE
1113 ></TD
1114 ></TR
1115 ></TABLE
1116 >
1117         </P
1118 ><P
1119 >       first. Run:
1120         </P
1121 ><P
1122 >       <TABLE
1123 BORDER="0"
1124 BGCOLOR="#E0E0E0"
1125 WIDTH="100%"
1126 ><TR
1127 ><TD
1128 ><PRE
1129 CLASS="PROGRAMLISTING"
1130 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
1131         </PRE
1132 ></TD
1133 ></TR
1134 ></TABLE
1135 >
1136         </P
1137 ><P
1138 >       Then do FIXME.
1139         </P
1140 ></DIV
1141 ><DIV
1142 CLASS="SECT2"
1143 ><H2
1144 CLASS="SECT2"
1145 ><A
1146 NAME="NEWRELEASE-AIX"
1147 >8.13. AIX</A
1148 ></H2
1149 ><P
1150 >       Login to Sourceforge's compilefarm via ssh:
1151         </P
1152 ><P
1153 >       <TABLE
1154 BORDER="0"
1155 BGCOLOR="#E0E0E0"
1156 WIDTH="100%"
1157 ><TR
1158 ><TD
1159 ><PRE
1160 CLASS="PROGRAMLISTING"
1161 >  ssh cf.sourceforge.net
1162         </PRE
1163 ></TD
1164 ></TR
1165 ></TABLE
1166 >
1167         </P
1168 ><P
1169 >       Choose the right operating system. If you have downloaded Privoxy
1170         before:
1171         </P
1172 ><P
1173 >       <TABLE
1174 BORDER="0"
1175 BGCOLOR="#E0E0E0"
1176 WIDTH="100%"
1177 ><TR
1178 ><TD
1179 ><PRE
1180 CLASS="PROGRAMLISTING"
1181 >  cd current
1182   cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1183   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
1184         </PRE
1185 ></TD
1186 ></TR
1187 ></TABLE
1188 >
1189         </P
1190 ><P
1191 >       If not, please <A
1192 HREF="http://www.privoxy.org/user-manual/user-manual/installation.html#INSTALLATION-SOURCE"
1193 TARGET="_top"
1194 >checkout
1195         Privoxy via CVS first</A
1196 >. Run:
1197         </P
1198 ><P
1199 >       <TABLE
1200 BORDER="0"
1201 BGCOLOR="#E0E0E0"
1202 WIDTH="100%"
1203 ><TR
1204 ><TD
1205 ><PRE
1206 CLASS="PROGRAMLISTING"
1207 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
1208         </PRE
1209 ></TD
1210 ></TR
1211 ></TABLE
1212 >
1213         </P
1214 ><P
1215 >       Then run:
1216         </P
1217 ><P
1218 >       <TABLE
1219 BORDER="0"
1220 BGCOLOR="#E0E0E0"
1221 WIDTH="100%"
1222 ><TR
1223 ><TD
1224 ><PRE
1225 CLASS="PROGRAMLISTING"
1226 >  make aix-dist
1227         </PRE
1228 ></TD
1229 ></TR
1230 ></TABLE
1231 >
1232         </P
1233 ><P
1234 >       which creates a gzip'ed tar archive. Sadly, you cannot use <B
1235 CLASS="COMMAND"
1236 >make
1237         aix-upload</B
1238 > on the Sourceforge machine (no ncftpput). You now have
1239         to manually upload the archive to Sourceforge's ftp server and release
1240         the file publicly.
1241         </P
1242 ></DIV
1243 ></DIV
1244 ><DIV
1245 CLASS="NAVFOOTER"
1246 ><HR
1247 ALIGN="LEFT"
1248 WIDTH="100%"><TABLE
1249 WIDTH="100%"
1250 BORDER="0"
1251 CELLPADDING="0"
1252 CELLSPACING="0"
1253 ><TR
1254 ><TD
1255 WIDTH="33%"
1256 ALIGN="left"
1257 VALIGN="top"
1258 ><A
1259 HREF="testing.html"
1260 >Prev</A
1261 ></TD
1262 ><TD
1263 WIDTH="34%"
1264 ALIGN="center"
1265 VALIGN="top"
1266 ><A
1267 HREF="index.html"
1268 >Home</A
1269 ></TD
1270 ><TD
1271 WIDTH="33%"
1272 ALIGN="right"
1273 VALIGN="top"
1274 ><A
1275 HREF="contact.html"
1276 >Next</A
1277 ></TD
1278 ></TR
1279 ><TR
1280 ><TD
1281 WIDTH="33%"
1282 ALIGN="left"
1283 VALIGN="top"
1284 >Testing Guidelines</TD
1285 ><TD
1286 WIDTH="34%"
1287 ALIGN="center"
1288 VALIGN="top"
1289 >&nbsp;</TD
1290 ><TD
1291 WIDTH="33%"
1292 ALIGN="right"
1293 VALIGN="top"
1294 >Contacting the developers, Bug Reporting and Feature Requests</TD
1295 ></TR
1296 ></TABLE
1297 ></DIV
1298 ></BODY
1299 ></HTML
1300 >