From c7eef8c67c4340f306002afd65efaaeb9b4fff87 Mon Sep 17 00:00:00 2001 From: floam Date: Mon, 20 Feb 2006 09:43:56 +0000 Subject: Use correct tag. git-svn-id: svn://svn.icculus.org/quake3/trunk@560 edf5b092-35ff-0310-97b2-ce42778d08ea --- web/include/get.php | 70 +++++++++++++++++++++++++++-------------------------- 1 file changed, 36 insertions(+), 34 deletions(-) (limited to 'web/include/get.php') diff --git a/web/include/get.php b/web/include/get.php index d5b15df..a8a12b6 100644 --- a/web/include/get.php +++ b/web/include/get.php @@ -26,13 +26,13 @@ done all of the work for you.

  • Packages for Ubuntu Linux. These are intended for Ubuntu Breezy.
  • -

    To install these, as root run dpkg -i - package.deb.

    +

    To install these, as root run dpkg -i + package.deb.

    There are also i686 binaries built on Ubuntu made by Pascal de Bruijn. Untar this into /opt/ or where ever you keep weird isolated installs. There is a decent chance these will work on most distributions, these are not - .debs.

    + .debs.

  • Fedora Core, RHEL

    @@ -44,8 +44,8 @@ done all of the work for you.

  • Gentoo

    -

    Gentoo users can just - emerge quake3 to get a recent snapshot of our Subversion repository.

    +

    Gentoo users can just + emerge quake3 to get a recent snapshot of our Subversion repository.

  • SUSE

    @@ -64,10 +64,10 @@ client.

    1. Change into a directory that you want the tree to be kept in.
    2. Check out the source tree:
      - svn co svn://svn.icculus.org/quake3/trunk quake3 + svn co svn://svn.icculus.org/quake3/trunk quake3
      (You can check out a specific revision with the -r option, like this: - svn co svn://svn.icculus.org/quake3/trunk quake3 -r100) + svn co svn://svn.icculus.org/quake3/trunk quake3 -r100)
    3. Read the README file. Really. Do it.
    4. @@ -81,49 +81,51 @@ client.

      Software, you still need to copy over legal PK3s like before.
    5. Change into the top level directory (it contains - the ui and - code directories.)
    6. -
    7. Run make.
    8. -
    9. Set $COPYDIR to the - directory you installed Quake3 to and make the copyfiles - target. Make sure you are changed to the owner of - this path (probably root).
      - COPYDIR="/opt/quake3" make copyfiles + the ui and + code directories.)
    10. +
    11. Run make.
    12. +
    13. Set $COPYDIR to the + directory you installed Quake3 to and make + the copyfiles target. Make sure you are + changed to the owner of this path (probably + root).
      + COPYDIR="/opt/quake3" make copyfiles
  • Mac OS X

    1. Change into the top level directory (it contains - the ui and - code directories.)
    2. -
    3. Run make.
    4. + the ui and + code directories.) +
    5. Run make.
    6. Install the latest point release for OS X.
    7. -
    8. Copy ioquake3.ppc - in build/release-darwin-ppc/ - to /Applications/Quake3/Quake3.app/Contents/MacOS/Quake3.
    9. +
    10. Copy ioquake3.ppc + in build/release-darwin-ppc/ + to /Applications/Quake3/Quake3.app/Contents/MacOS/Quake3.
    11. You need a libSDL-1.2.0.dylib in that .app's MacOS directory.
    12. -
    13. You need to copy your pak0.pk3 - from your Quake 3 CD-ROM's /baseq3 - directory to your /Applications/Quake3/baseq3 +
    14. You need to copy your pak0.pk3 + from your Quake 3 CD-ROM's /baseq3 + directory to your /Applications/Quake3/baseq3 directory.
    15. Ditto for the Team Arena mission pack, though - you would be substituting baseq3 - in the above example for missionpack.
    16. + you would be substituting baseq3 + in the above example for missionpack.

    After you've done all of that, you can double click - on the .app file, or change to - the /Applications/Quake3/ directory - in a terminal and run the binary. + on the .app file, or change to + the /Applications/Quake3/ directory in a terminal + and run the binary.

  • Windows

    -

    Building on Windows is slightly complicated. You can either - use Microsoft Visual C++ or MinGW. MinGW works better currently; - both methods are described in the +

    Building on Windows is slightly complicated. + You can either use Microsoft Visual C++ or MinGW. + MinGW works better currently; both methods are described + in the README - you already are supposed to have read.

    + that you already are supposed to have read.

  • @@ -132,7 +134,7 @@ client.

    Point Release Installers

    The id software patches are still needed before installing -this project because they contain updated pk3 +this project because they contain updated .pk3 files. We mirror them for your convenience: