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