[BACK]Return to CVS.txt CVS log [TXT][DIR] Up to [local] / OpenXM_contrib / pari-2.2

Diff for /OpenXM_contrib/pari-2.2/Attic/CVS.txt between version 1.1 and 1.2

version 1.1, 2001/10/02 11:16:55 version 1.2, 2002/09/11 07:26:37
Line 1 
Line 1 
 The Concurrent Versions System (or CVS, see http://www.cyclic.com) provides  The Concurrent Versions System (CVS, see http://www.cyclic.com) provides
 network-transparent source control for groups of developers. For ordinary  network-transparent source control for groups of developers. For ordinary
 users it provides a very convenient way to obtain patched versions in between  users it provides a very convenient way to obtain patched versions in between
 releases. CVS clients are available for most major platforms: Unix, MacOS,  releases. CVS clients are available for most major platforms: Unix, MacOS,
Line 6  Windows (see http://www.wincvs.org/).
Line 6  Windows (see http://www.wincvs.org/).
   
 This file documents access to the PARI CVS server, which is intended for  This file documents access to the PARI CVS server, which is intended for
 PARI lovers who want the very latest bleeding edge release. The CVS sources  PARI lovers who want the very latest bleeding edge release. The CVS sources
 compile cleanly and pass the bench suite on (one of) the administrator(s)'s  may contain severe bugs, benches may fail, they may not even compile. Stable
 machine(s), they may otherwise contain severe bugs. Stable releases are  releases are made available on a regular basis using the customary method:
 made available on a regular basis using the customary method: a message to  a message to pari-announce.
 pari-announce.  
   
 1) First connection to the anonymous CVS server:  1) First connection to the anonymous CVS server:
 ================================================  ================================================
Line 35  directly (without the cryptic -d argument), as long as
Line 34  directly (without the cryptic -d argument), as long as
 ======================  ======================
   
 * You can build pari in the usual way (see INSTALL) as if this 'pari'  * You can build pari in the usual way (see INSTALL) as if this 'pari'
 directory had been created by fetching then extracting an archive on an FTP  directory had been created by fetching, then extracting, an archive on an FTP
 server.  server.
   
 * You can update your local copy at any time using 'cvs update', which will  * You can update your local copy at any time using 'cvs update', which will
Line 45  put you in synch with the repository.
Line 44  put you in synch with the repository.
 by using 'cvs diff'. If you modify some files on your local copy, this also  by using 'cvs diff'. If you modify some files on your local copy, this also
 enables you to track down your changes, and produce a patch. You won't be  enables you to track down your changes, and produce a patch. You won't be
 able to commit your changes using anonymous access. Send the output of 'cvs  able to commit your changes using anonymous access. Send the output of 'cvs
 diff' [with flag -c if your local diff supports it] to the pari-dev mailing  diff' [ with flag -c if your local diff supports it ] to the pari-dev mailing
 list with a short description of what you've done, or to  list with a short description of what you've done, or to
 pari@math.u-bordeaux.fr if you're not subscribed to pari-dev.  pari@math.u-bordeaux.fr if you're not subscribed to pari-dev.
   
Line 56  Once this is granted, you'll be able to log in as 'cvs
Line 55  Once this is granted, you'll be able to log in as 'cvs
 administrator) instead of 'cvs' (CVS user) as described above and you'll be  administrator) instead of 'cvs' (CVS user) as described above and you'll be
 able to use 'cvs commit'.  able to use 'cvs commit'.
   
   3) Version tags:
   ================
   
 NOTES and CAVEATS:  All project files have an individual version number, independent of the
 ==================  release numbering scheme. Official releases (starting from version 2.0.17)
   are 'tagged' so that all files pertaining to a given release can be
   simultaneously accessed without tracking version numbers. Tag names are
   'release-<VERSION>' with dots replaced by dashes, e.g 'release-2-0-20' for
   2.0.20.
   
   If you want to fetch a specific version of pari (2.0.17 or more recent), add
   the argument '-r <TAG>' to your checkout or update command. The tag
   'release-2-1-patches' denotes the stable branch 2.1 as a whole, and can be
   used to checkout up to date sources from that branch in between releases. For
   instance:
   
     cvs update -r release-2-1-patches
   
   produces the latest stable distribution with all relevant patches [the ones
   not affecting stability] backported.
   
   TIPS and CAVEATS:
   =================
 * you can speed up file transfers by using cvs -z3 (transfer files in  * you can speed up file transfers by using cvs -z3 (transfer files in
 compressed format), e.g 'cvs -z3 update' if you've missed a lot of patches,  compressed format), e.g 'cvs -z3 update' if you've missed a lot of patches,
 or 'cvs -z3 checkout' for the initial checkout. This requires that GNU gzip  or 'cvs -z3 checkout' for the initial checkout. This requires that GNU gzip
 be in your path. You can create a .cvsrc file in your home directory  be in your path.
 containing lines of the form:  
   
   * You can create a .cvsrc file in your home directory containing lines of the
   form:
   
     cvs -z3          [ use gzip -3 for all transfers ]      cvs -z3          [ use gzip -3 for all transfers ]
     diff -c          [ use diff -c (context diff) by default in 'cvs diff' ]      diff -c          [ use diff -c (context diff) by default in 'cvs diff' ]
   
 * once you've run Configure, some files/directory will be created in the  
 local copy which are not under CVS control (only the master files are).  
 These are  
   
   O<OS>-<arch>*  
   Makefile.O<OS>-<arch>*  
   examples/Makefile.<OS>-<arch>  
   doc/Makefile  
   doc/gphelp  
   doc/paricfg.tex  
   doc/*.[aux | dvi | idx | log | ps | std | toc]  
   emacs/pari.el  
   
 After a global 'cvs diff', or 'cvs status', you can safely ignore all  
 messages pertaining to them (e.g "? doc/Makefile").  
   
 * 'cvs diff' gives you the difference between your local copy and the  * 'cvs diff' gives you the difference between your local copy and the
 sources they were based on, not with the current state of the repository.  sources they were based on, not with the current state of the repository.
 Use 'cvs diff -D now' for that.  Use 'cvs diff -D now' for that.
   
 * All project files have an individual version number, independant of the  
 release numbering scheme. Official releases (starting from version 2.0.17)  
 are 'tagged' so that all files pertaining to a given release can be  
 simultaneously accessed without tracking version numbers. Tag names are  
 'release-VERSION', e.g 'release-2-0-20'.  
   
 * On Windows 95/98/2000 + Cygwin, you may have to explicitly set HOME (e.g  * On Windows 95/98/2000 + Cygwin, you may have to explicitly set HOME (e.g
 in your .bashrc) to some existing directory otherwise CVS will abort on  in your .bashrc) to some existing directory otherwise CVS will abort on
Legend:
Removed from v.1.1  
changed lines
  Added in v.1.2
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>