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