Difference between revisions of "Fs2 open on Linux/Acquiring the Code"

From FreeSpace Wiki
Jump to: navigation, search
(Add note about needing CVS, link to Installing CVS)
(Added instructions for stable branch co)
Line 11: Line 11:
 
Now get the source. Run from a terminal:
 
Now get the source. Run from a terminal:
 
  $ cvs -d:pserver:anonymous:[email protected]:/home/fs2source/cvsroot login
 
  $ cvs -d:pserver:anonymous:[email protected]:/home/fs2source/cvsroot login
and then
+
This tells the CVS tool to first use a password file for authentication (pserver), that you are user "anonymous" with the password "anonymous" who wants to access warpcore.org's CVS repository "/home/fs2source/cvsroot" and login.<br><br>
 +
Next, get the code from the server we just connected to, either from the development branch:
 
  $ cvs -z3 -d:pserver:[email protected]:/home/fs2source/cvsroot co fs2_open
 
  $ cvs -z3 -d:pserver:[email protected]:/home/fs2source/cvsroot co fs2_open
The first cvs command tells the CVS tool to first use a password file for authentication (pserver), that you are user "anonymous" with the password "anonymous" who wants to access warpcore.org's CVS repository "/home/fs2source/cvsroot" and login. The second command tells the CVS server on which we are now connected to that we want to checkout (co) the fs2_open module.
+
..or from the "stable branch" (currently 3.6.9):
 +
$ cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co -r fs2_open_3_6_9 fs2_open
 +
{{Note| For just playing the game it is usually best to get the code from the "stable branch", as it will generally be more.. stable.}}
 +
Both of the last two commands tell the CVS server that we want to checkout (co) the CVS module "fs2_open". Either from the default branch (the development branch - HEAD) or from the branch determined by the "-r" option.
 
<br>
 
<br>

Revision as of 20:21, 26 October 2007

« Installing the Development Libraries The fs2_open on Linux Guide
Acquiring the Code
Checkout Script »

Note: This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary executable.

Before you begin, make sure you have write permissions on your current working directory. $HOME/$USER is a pretty safe bet. I recommend that you create a permanent /$HOME/$USER/src directory from which you run the CVS command, this way CVS will only update the files changed the next time you download the source and it's always nice to have things organized. Make sure you have CVS installed on your system. See the Installing CVS chapter on installing CVS.

Now get the source. Run from a terminal:

$ cvs -d:pserver:anonymous:[email protected]:/home/fs2source/cvsroot login

This tells the CVS tool to first use a password file for authentication (pserver), that you are user "anonymous" with the password "anonymous" who wants to access warpcore.org's CVS repository "/home/fs2source/cvsroot" and login.

Next, get the code from the server we just connected to, either from the development branch:

$ cvs -z3 -d:pserver:[email protected]:/home/fs2source/cvsroot co fs2_open

..or from the "stable branch" (currently 3.6.9):

$ cvs -z3 -d:pserver:[email protected]:/home/fs2source/cvsroot co -r fs2_open_3_6_9 fs2_open
Note: For just playing the game it is usually best to get the code from the "stable branch", as it will generally be more.. stable.

Both of the last two commands tell the CVS server that we want to checkout (co) the CVS module "fs2_open". Either from the default branch (the development branch - HEAD) or from the branch determined by the "-r" option.