[Devil-linux-commit] docs/developer new-developer.txt,NONE,1.1

[<fr...@pr...>]

Update of /cvsroot/devil-linux/docs/developer
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv11508/developer

Added Files:
	new-developer.txt 
Log Message:
add documentation for admins and newcomers


--- NEW FILE: new-developer.txt ---
You've just become a new Devil-Linux Developer. So what is there
that is different from before? Let me give you a short getting 
started guide:

  * If you have not done so before run "ssh-keygen -t rsa" from the 
    account you will be doing you development at. Hit enter till you 
    are back at the prompt.

  * Go to http://sourceforge.net/account/editsshkeys.php (might need
    to log in to SF first if you are not prompted for your password)

  * Run "cat ~/.ssh/id_rsa.pub" and copy and paste this into the text 
    box on the page referenced above and click "Update" below the box.

    The output is actually _one_ line like the following (folded for readability):

       ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAp1gM1XLESnStKjFd4zpxxVgA4aZqa
       DPVufJJUnVYwU0FBiMWJbDXXXSn4tY/KbWWKhYBbnRVZzSY0YmhGdKQoYyrQqJy7S
       sOdFkWGkay9FOgub526r2mxjnn/0fnripE6NMHaaUjLHldR4WtYvwb1tpQSiQPqWZ
       8f0a7KMVjsFM= user@host

    It takes some hours (maybe up to 24 or so) till your ssh private key is
    installed on the CVS server. In the meantime you have to enter your SF
    password everytime you run the cvs command.

  * Add this to the files mentioned:

    "~/.bashrc":
      export CVS_RSH=ssh
      export SFUSER=XXXXXXXXX       # replace XXXXXXXXX with your 
                                    # SourceForge username
      test -s ~/.alias && . ~/.alias

    "~/.alias":
      alias cvs_sf='cvs -z3 -d:ext:${SFUSER}@cvs.sourceforge.net:/cvsroot/devil-linux'

  * Let's test this right aways. So either login again or open a new
    "konsole" (if you use KDE), or a new shell. 
    
    Check with "alias cvs_sf" that the alias exists and the run "cvs_sf
    checkout -c" which should show you the modules that you can check out,
    eg.
    
      # cvs_sf checkout -c
      build        build
      docs         docs
      scripts      scripts
      web          web

  * You possibly already checked out the build module before you 
    became a developer. Now you need to check out everything again.
    So run eg.
      cvs_sf checkout build    # note: need to specify 'cvs_sf'
    to get the up to date build system.
    
    In the future you get the latest updates via eg.
    
      cd build
      cvs update -d -P         # note: no need to specify 'cvs_sf' here
      
    If you don't do that you always have to use 'cvs_sf' !!!


Hope that should get you going as fast as possible. If I've
forgotten something it's because it has been such a long time
when I had to do all this ;-)

Friedrich Lobenstock <fl...@fl...>
$Id: new-developer.txt,v 1.1 2004/01/28 22:09:28 friedl Exp $