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