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