apr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@locus.apache.org
Subject cvs commit: apr-site anoncvs.txt index.html
Date Mon, 20 Nov 2000 22:44:16 GMT
rbb         00/11/20 14:44:15

  Modified:    .        index.html
  Added:       .        anoncvs.txt
  Log:
  Add instructions for getting the APR code from CVS.  This was basically
  taken from Apache and modified slightly.
  
  Revision  Changes    Path
  1.6       +3 -0      apr-site/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /home/cvs/apr-site/index.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- index.html	2000/11/16 22:02:57	1.5
  +++ index.html	2000/11/20 22:44:15	1.6
  @@ -27,5 +27,8 @@
     <H3><center>The Library API</center></H3>
     APR uses ScanDoc to generate all of the API docs in 
     <a href=docs/index.html>HTML format</a>.
  +
  +  <H3><center>How to contribute</center></H3>
  +  <a href=anoncvs.html>Getting</a> the source code
    </body>
   </html>
  
  
  
  1.1                  apr-site/anoncvs.txt
  
  Index: anoncvs.txt
  ===================================================================
  Anonymous CVS access is available again, but on a different system
  than before.  In addition to the anonymous CVS repository, there is
  also
  
      <http://www.apache.org/websrc/viewcvs.cgi/>
  
  and an rsync server at dev.apache.org.  Try
  
      rsync dev.apache.org::
  
  to get a listing of the modules.
  
      rsync -avz dev.apache.org::module-name local-directory-name
  
  to grab or update a local copy of the "module-name" sources.
  
  ======================================================================
                            HOW TO USE ANONCVS
  ======================================================================
  
  Developers with commit access to the Apache source tree normally
  use CVS to keep their local copies of the source tree up to date
  automatically.  This is a very useful ability that also allows
  for getting change history of files, diffs between arbitrary 
  versions, etc.  This is also the method used to commit changes 
  to the source tree.
  
  For those who do not have commit access to the source tree, anoncvs
  offers an alternative way to do most of this using a copy of the
  CVS repository.  The big difference is, of course, that you can't
  commit changes using anoncvs.
  
  The first step in using anoncvs is setting your CVSROOT environment 
  variable.  This tells CVS to what server it should connect.  There
  are currently two, and the only available method to access these
  anoncvs servers is pserver; you need a reasonably recent CVS client
  to use it.  An example of setting it from a Bourne shell:
  
    user@host:~$ CVSROOT=:pserver:anoncvs@www.apache.org:/home/cvspublic
    user@host:~$ export CVSROOT
  
  It is very important that you do not put a trailing "/" on the value
  of CVSROOT.
  
  The two anoncvs servers currently available are:
  
    :pserver:anoncvs@www.apache.org:/home/cvspublic
  
  and
  
    :pserver:anoncvs@CVS.Sourcery.Org:/cvs/apache
  
  Choose one of these values for your setting of CVSROOT.
  Once you have set your CVSROOT, you need to log in:
  
    user@host:~$ cvs login
    (Logging in to anoncvs@www.apache.org:/home/cvspublic)
    CVS password: 
  
  The password is "anoncvs" (without the quotation marks) for
  both servers.
  
  To check out the current development tree:
  
    user@host:~$ cvs checkout apr
    U apr/APRDesign
    U apr/APRVARS.in
    U apr/Makefile.in
    U apr/acconfig.h
    [...]
    U apr/user/unix/.cvsignore
    U apr/user/unix/Makefile.in
    U apr/user/unix/homedir.c
  
  
  To update your local tree to the latest version:
  
    user@host:~$ cvs update -dP apr
  
  or
  
    user@host:~/apr$ cvs update -dP .
  
  etc.  
  
    P core/buff.c
    P core/conf.h
    RCS file: /home/cvs/apache-1.3/src/core/http_core.c,v
    retrieving revision 1.109
    retrieving revision 1.110
    Merging differences between 1.109 and 1.110 into http_core.c
    M core/http_core.c
  
  The P means that the local copy was patched to update it to the 
  current version.  The M means that your local copy was modified,
  but that the changes were merged into your copy successfully.  If
  you see a C that means that there was a conflict in merging 
  the changes and that you need to review the file manually (hint: 
  search for >>>> in the file) to merge the changes.
  
  To obtain a diff of changes between your checked out copy and 
  the source tree at the time you checked it out:
  
    user@host:~$ cvs diff -u apr
  
  To obtain a diff against the current source tree, be sure to
  do an update before the diff.
  
  The idea of having an anoncvs server is to make it much easier
  for people interested in doing development to have access to the
  CVS tree so they can submit patches against the current source
  tree and can keep their patched version up to date without 
  having to manually merge their patches all the time.
  
  
  

Mime
View raw message