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 >        You should ensure you have the latest version of Cygwin (from
 670         <A
 671 HREF="http://www.cygwin.com/"
 672 TARGET="_top"
 673 >http://www.cygwin.com/</A
 674 >).
 675         Run the following commands from within a Cygwin bash shell.
 676       </P
 677 ><P
 678 >        First check out a clean copy of the correct code version, by running:
 679       </P
 680 ><P
 681 >      <TABLE
 682 BORDER="0"
 683 BGCOLOR="#E0E0E0"
 684 WIDTH="100%"
 685 ><TR
 686 ><TD
 687 ><PRE
 688 CLASS="PROGRAMLISTING"
 689 >        mkdir dist
 690         cd dist
 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 .
 693       </PRE
 694 ></TD
 695 ></TR
 696 ></TABLE
 697 >
 698       </P
 699 ><P
 700 >        (Note: It is important that this is a clean copy of the code,
 701         do not re-use a working directory after you have manually compiled
 702         there).
 703       </P
 704 ><P
 705 >        Then you can build the package.  This is fully automated, and is
 706         controlled by <TT
 707 CLASS="FILENAME"
 708 >winsetup/GNUmakefile</TT
 709 >.
 710         All you need to do is:
 711       </P
 712 ><P
 713 >      <TABLE
 714 BORDER="0"
 715 BGCOLOR="#E0E0E0"
 716 WIDTH="100%"
 717 ><TR
 718 ><TD
 719 ><PRE
 720 CLASS="PROGRAMLISTING"
 721 >        cd winsetup
 722         make
 723       </PRE
 724 ></TD
 725 ></TR
 726 ></TABLE
 727 >
 728       </P
 729 ><P
 730 >        Now you can manually rename <TT
 731 CLASS="FILENAME"
 732 >privoxy_setup.exe</TT
 733 > to
 734         <TT
 735 CLASS="FILENAME"
 736 >privoxy_setup_X_Y_Z.exe</TT
 737 >, and upload it to
 738         SourceForge.
 739       </P
 740 ></DIV
 741 ><DIV
 742 CLASS="SECT2"
 743 ><H2
 744 CLASS="SECT2"
 745 ><A
 746 NAME="NEWRELEASE-DEBIAN"
 747 >8.7. Debian</A
 748 ></H2
 749 ><P
 750 >       Ensure that you have the latest code version. Hence run:
 751         </P
 752 ><P
 753 >       <TABLE
 754 BORDER="0"
 755 BGCOLOR="#E0E0E0"
 756 WIDTH="100%"
 757 ><TR
 758 ><TD
 759 ><PRE
 760 CLASS="PROGRAMLISTING"
 761 >  cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
 762   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
 763   cd current
 764         </PRE
 765 ></TD
 766 ></TR
 767 ></TABLE
 768 >
 769         </P
 770 ><P
 771 >       first. Run:
 772         </P
 773 ><P
 774 >       <TABLE
 775 BORDER="0"
 776 BGCOLOR="#E0E0E0"
 777 WIDTH="100%"
 778 ><TR
 779 ><TD
 780 ><PRE
 781 CLASS="PROGRAMLISTING"
 782 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
 783         </PRE
 784 ></TD
 785 ></TR
 786 ></TABLE
 787 >
 788         </P
 789 ><P
 790 >       Then do FIXME.
 791         </P
 792 ></DIV
 793 ><DIV
 794 CLASS="SECT2"
 795 ><H2
 796 CLASS="SECT2"
 797 ><A
 798 NAME="NEWRELEASE-MACOSX"
 799 >8.8. Mac OSX</A
 800 ></H2
 801 ><P
 802 >       Ensure that you have the latest code version. Hence run:
 803         </P
 804 ><P
 805 >       <TABLE
 806 BORDER="0"
 807 BGCOLOR="#E0E0E0"
 808 WIDTH="100%"
 809 ><TR
 810 ><TD
 811 ><PRE
 812 CLASS="PROGRAMLISTING"
 813 >  cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
 814   cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
 815   cd ..
 816   cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co osxsetup
 817         </PRE
 818 ></TD
 819 ></TR
 820 ></TABLE
 821 >
 822         </P
 823 ><P
 824 >       From the osxsetup directory, run:
 825         <TABLE
 826 BORDER="0"
 827 BGCOLOR="#E0E0E0"
 828 WIDTH="100%"
 829 ><TR
 830 ><TD
 831 ><PRE
 832 CLASS="PROGRAMLISTING"
 833 >  build
 834         </PRE
 835 ></TD
 836 ></TR
 837 ></TABLE
 838 >
 839         </P
 840 ><P
 841 >       This will run <TT
 842 CLASS="FILENAME"
 843 >autoheader</TT
 844 >, <TT
 845 CLASS="FILENAME"
 846 >autoconf</TT
 847 > and
 848         <TT
 849 CLASS="FILENAME"
 850 >configure</TT
 851 > as well as <TT
 852 CLASS="FILENAME"
 853 >make</TT
 854 >.
 855         Finally, it will copy over the necessary files to the ./osxsetup/files directory
 856         for further processing by <TT
 857 CLASS="FILENAME"
 858 >PackageMaker</TT
 859 >.
 860         </P
 861 ><P
 862 >       Bring up PackageMaker with the PrivoxyPackage.pmsp definition file, modify the package
 863         name to match the release, and hit the "Create package" button.
 864         If you specify ./Privoxy.pkg as the output package name, you can then create
 865         the distributable zip file with the command:
 866         <TABLE
 867 BORDER="0"
 868 BGCOLOR="#E0E0E0"
 869 WIDTH="100%"
 870 ><TR
 871 ><TD
 872 ><PRE
 873 CLASS="PROGRAMLISTING"
 874 >zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg
 875         </PRE
 876 ></TD
 877 ></TR
 878 ></TABLE
 879 >
 880         You can then upload <TT
 881 CLASS="FILENAME"
 882 >privoxyosx_setup_x.y.z.zip</TT
 883 > anonymously to
 884         <TT
 885 CLASS="FILENAME"
 886 >uploads.sourceforge.net/incoming</TT
 887 >,
 888         create a release for it, and you're done.
 889         </P
 890 ></DIV
 891 ><DIV
 892 CLASS="SECT2"
 893 ><H2
 894 CLASS="SECT2"
 895 ><A
 896 NAME="NEWRELEASE-FREEBSD"
 897 >8.9. FreeBSD</A
 898 ></H2
 899 ><P
 900 >       Change the version number of <SPAN
 901 CLASS="APPLICATION"
 902 >Privoxy</SPAN
 903 > in the
 904         configure.in file. Run:
 905         <TABLE
 906 BORDER="0"
 907 BGCOLOR="#E0E0E0"
 908 WIDTH="100%"
 909 ><TR
 910 ><TD
 911 ><PRE
 912 CLASS="PROGRAMLISTING"
 913 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
 914         </PRE
 915 ></TD
 916 ></TR
 917 ></TABLE
 918 >
 919         Then ...
 920       </P
 921 ><P
 922 >       Login to Sourceforge's compilefarm via ssh:
 923         </P
 924 ><P
 925 >       <TABLE
 926 BORDER="0"
 927 BGCOLOR="#E0E0E0"
 928 WIDTH="100%"
 929 ><TR
 930 ><TD
 931 ><PRE
 932 CLASS="PROGRAMLISTING"
 933 >  ssh cf.sourceforge.net
 934         </PRE
 935 ></TD
 936 ></TR
 937 ></TABLE
 938 >
 939         </P
 940 ><P
 941 >       Choose the right operating system.
 942         </P
 943 ><P
 944 >       <TABLE
 945 BORDER="0"
 946 BGCOLOR="#E0E0E0"
 947 WIDTH="100%"
 948 ><TR
 949 ><TD
 950 ><PRE
 951 CLASS="PROGRAMLISTING"
 952 >  cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
 953   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
 954   cd current
 955         </PRE
 956 ></TD
 957 ></TR
 958 ></TABLE
 959 >
 960         </P
 961 ><P
 962 >       Run:
 963         </P
 964 ><P
 965 >       <TABLE
 966 BORDER="0"
 967 BGCOLOR="#E0E0E0"
 968 WIDTH="100%"
 969 ><TR
 970 ><TD
 971 ><PRE
 972 CLASS="PROGRAMLISTING"
 973 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
 974         </PRE
 975 ></TD
 976 ></TR
 977 ></TABLE
 978 >
 979         </P
 980 ><P
 981 >       Then run:
 982         </P
 983 ><P
 984 >       <TABLE
 985 BORDER="0"
 986 BGCOLOR="#E0E0E0"
 987 WIDTH="100%"
 988 ><TR
 989 ><TD
 990 ><PRE
 991 CLASS="PROGRAMLISTING"
 992 >  gmake freebsd-dist
 993         </PRE
 994 ></TD
 995 ></TR
 996 ></TABLE
 997 >
 998         </P
 999 ><P
1000 >       which creates a gzip'ed tar archive. Sadly, you cannot use <B
1001 CLASS="COMMAND"
1002 >make
1003         freebsd-upload</B
1004 > on the Sourceforge machine (no ncftpput). You now have
1005         to manually upload the archive to Sourceforge's ftp server and release
1006         the file publicly.
1007         </P
1008 ></DIV
1009 ><DIV
1010 CLASS="SECT2"
1011 ><H2
1012 CLASS="SECT2"
1013 ><A
1014 NAME="NEWRELEASE-TARBALL"
1015 >8.10. Tarball</A
1016 ></H2
1017 ><P
1018 >       Ensure that you have the right code version. Hence run:
1019         </P
1020 ><P
1021 >       <TABLE
1022 BORDER="0"
1023 BGCOLOR="#E0E0E0"
1024 WIDTH="100%"
1025 ><TR
1026 ><TD
1027 ><PRE
1028 CLASS="PROGRAMLISTING"
1029 >  cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1030   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
1031   cd current
1032         </PRE
1033 ></TD
1034 ></TR
1035 ></TABLE
1036 >
1037         </P
1038 ><P
1039 >       first. Run:
1040         </P
1041 ><P
1042 >       <TABLE
1043 BORDER="0"
1044 BGCOLOR="#E0E0E0"
1045 WIDTH="100%"
1046 ><TR
1047 ><TD
1048 ><PRE
1049 CLASS="PROGRAMLISTING"
1050 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
1051         </PRE
1052 ></TD
1053 ></TR
1054 ></TABLE
1055 >
1056         </P
1057 ><P
1058 >       Then do:
1059         </P
1060 ><P
1061 >       <TABLE
1062 BORDER="0"
1063 BGCOLOR="#E0E0E0"
1064 WIDTH="100%"
1065 ><TR
1066 ><TD
1067 ><PRE
1068 CLASS="PROGRAMLISTING"
1069 >  make tarball-dist
1070         </PRE
1071 ></TD
1072 ></TR
1073 ></TABLE
1074 >
1075         </P
1076 ><P
1077 >       To upload the package to Sourceforge, simply issue
1078         </P
1079 ><P
1080 >       <TABLE
1081 BORDER="0"
1082 BGCOLOR="#E0E0E0"
1083 WIDTH="100%"
1084 ><TR
1085 ><TD
1086 ><PRE
1087 CLASS="PROGRAMLISTING"
1088 >  make tarball-upload
1089         </PRE
1090 ></TD
1091 ></TR
1092 ></TABLE
1093 >
1094         </P
1095 ><P
1096 >       Goto the displayed URL and release the file publicly on Sourceforge.
1097       </P
1098 ></DIV
1099 ><DIV
1100 CLASS="SECT2"
1101 ><H2
1102 CLASS="SECT2"
1103 ><A
1104 NAME="NEWRELEASE-HPUX"
1105 >8.11. HP-UX 11</A
1106 ></H2
1107 ><P
1108 >       Ensure that you have the latest code version. Hence run:
1109         </P
1110 ><P
1111 >       <TABLE
1112 BORDER="0"
1113 BGCOLOR="#E0E0E0"
1114 WIDTH="100%"
1115 ><TR
1116 ><TD
1117 ><PRE
1118 CLASS="PROGRAMLISTING"
1119 >  cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1120   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
1121   cd current
1122         </PRE
1123 ></TD
1124 ></TR
1125 ></TABLE
1126 >
1127         </P
1128 ><P
1129 >       first. Run:
1130         </P
1131 ><P
1132 >       <TABLE
1133 BORDER="0"
1134 BGCOLOR="#E0E0E0"
1135 WIDTH="100%"
1136 ><TR
1137 ><TD
1138 ><PRE
1139 CLASS="PROGRAMLISTING"
1140 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
1141         </PRE
1142 ></TD
1143 ></TR
1144 ></TABLE
1145 >
1146         </P
1147 ><P
1148 >       Then do FIXME.
1149         </P
1150 ></DIV
1151 ><DIV
1152 CLASS="SECT2"
1153 ><H2
1154 CLASS="SECT2"
1155 ><A
1156 NAME="NEWRELEASE-AMIGA"
1157 >8.12. Amiga OS</A
1158 ></H2
1159 ><P
1160 >       Ensure that you have the latest code version. Hence run:
1161         </P
1162 ><P
1163 >       <TABLE
1164 BORDER="0"
1165 BGCOLOR="#E0E0E0"
1166 WIDTH="100%"
1167 ><TR
1168 ><TD
1169 ><PRE
1170 CLASS="PROGRAMLISTING"
1171 >  cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1172   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
1173   cd current
1174         </PRE
1175 ></TD
1176 ></TR
1177 ></TABLE
1178 >
1179         </P
1180 ><P
1181 >       first. Run:
1182         </P
1183 ><P
1184 >       <TABLE
1185 BORDER="0"
1186 BGCOLOR="#E0E0E0"
1187 WIDTH="100%"
1188 ><TR
1189 ><TD
1190 ><PRE
1191 CLASS="PROGRAMLISTING"
1192 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
1193         </PRE
1194 ></TD
1195 ></TR
1196 ></TABLE
1197 >
1198         </P
1199 ><P
1200 >       Then do FIXME.
1201         </P
1202 ></DIV
1203 ><DIV
1204 CLASS="SECT2"
1205 ><H2
1206 CLASS="SECT2"
1207 ><A
1208 NAME="NEWRELEASE-AIX"
1209 >8.13. AIX</A
1210 ></H2
1211 ><P
1212 >       Login to Sourceforge's compilefarm via ssh:
1213         </P
1214 ><P
1215 >       <TABLE
1216 BORDER="0"
1217 BGCOLOR="#E0E0E0"
1218 WIDTH="100%"
1219 ><TR
1220 ><TD
1221 ><PRE
1222 CLASS="PROGRAMLISTING"
1223 >  ssh cf.sourceforge.net
1224         </PRE
1225 ></TD
1226 ></TR
1227 ></TABLE
1228 >
1229         </P
1230 ><P
1231 >       Choose the right operating system. If you have downloaded Privoxy
1232         before:
1233         </P
1234 ><P
1235 >       <TABLE
1236 BORDER="0"
1237 BGCOLOR="#E0E0E0"
1238 WIDTH="100%"
1239 ><TR
1240 ><TD
1241 ><PRE
1242 CLASS="PROGRAMLISTING"
1243 >  cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
1244   cvs -z3  -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa export -r  v_X_Y_Z current
1245   cd current
1246         </PRE
1247 ></TD
1248 ></TR
1249 ></TABLE
1250 >
1251         </P
1252 ><P
1253 >       If not, please <A
1254 HREF="http://www.privoxy.org/user-manual/user-manual/installation.html#INSTALLATION-SOURCE"
1255 TARGET="_top"
1256 >checkout
1257         Privoxy via CVS first</A
1258 >. Run:
1259         </P
1260 ><P
1261 >       <TABLE
1262 BORDER="0"
1263 BGCOLOR="#E0E0E0"
1264 WIDTH="100%"
1265 ><TR
1266 ><TD
1267 ><PRE
1268 CLASS="PROGRAMLISTING"
1269 >  autoheader &#38;&#38; autoconf &#38;&#38; ./configure
1270         </PRE
1271 ></TD
1272 ></TR
1273 ></TABLE
1274 >
1275         </P
1276 ><P
1277 >       Then run:
1278         </P
1279 ><P
1280 >       <TABLE
1281 BORDER="0"
1282 BGCOLOR="#E0E0E0"
1283 WIDTH="100%"
1284 ><TR
1285 ><TD
1286 ><PRE
1287 CLASS="PROGRAMLISTING"
1288 >  make aix-dist
1289         </PRE
1290 ></TD
1291 ></TR
1292 ></TABLE
1293 >
1294         </P
1295 ><P
1296 >       which creates a gzip'ed tar archive. Sadly, you cannot use <B
1297 CLASS="COMMAND"
1298 >make
1299         aix-upload</B
1300 > on the Sourceforge machine (no ncftpput). You now have
1301         to manually upload the archive to Sourceforge's ftp server and release
1302         the file publicly.
1303         </P
1304 ></DIV
1305 ></DIV
1306 ><DIV
1307 CLASS="NAVFOOTER"
1308 ><HR
1309 ALIGN="LEFT"
1310 WIDTH="100%"><TABLE
1311 WIDTH="100%"
1312 BORDER="0"
1313 CELLPADDING="0"
1314 CELLSPACING="0"
1315 ><TR
1316 ><TD
1317 WIDTH="33%"
1318 ALIGN="left"
1319 VALIGN="top"
1320 ><A
1321 HREF="testing.html"
1322 >Prev</A
1323 ></TD
1324 ><TD
1325 WIDTH="34%"
1326 ALIGN="center"
1327 VALIGN="top"
1328 ><A
1329 HREF="index.html"
1330 >Home</A
1331 ></TD
1332 ><TD
1333 WIDTH="33%"
1334 ALIGN="right"
1335 VALIGN="top"
1336 ><A
1337 HREF="contact.html"
1338 >Next</A
1339 ></TD
1340 ></TR
1341 ><TR
1342 ><TD
1343 WIDTH="33%"
1344 ALIGN="left"
1345 VALIGN="top"
1346 >Testing Guidelines</TD
1347 ><TD
1348 WIDTH="34%"
1349 ALIGN="center"
1350 VALIGN="top"
1351 >&nbsp;</TD
1352 ><TD
1353 WIDTH="33%"
1354 ALIGN="right"
1355 VALIGN="top"
1356 >Contacting the developers, Bug Reporting and Feature Requests</TD
1357 ></TR
1358 ></TABLE
1359 ></DIV
1360 ></BODY
1361 ></HTML
1362 >