Return to CVS.txt CVS log

Up to [local] / OpenXM_contrib / pari-2.2

Annotation of OpenXM_contrib/pari-2.2/CVS.txt, Revision 1.1.1.1

1.1       noro        1: The Concurrent Versions System (or CVS, see http://www.cyclic.com) provides
                      2: network-transparent source control for groups of developers. For ordinary
                      3: users it provides a very convenient way to obtain patched versions in between
                      4: releases. CVS clients are available for most major platforms: Unix, MacOS,
                      5: Windows (see http://www.wincvs.org/).
                      6:
                      7: This file documents access to the PARI CVS server, which is intended for
                      8: PARI lovers who want the very latest bleeding edge release. The CVS sources
                      9: compile cleanly and pass the bench suite on (one of) the administrator(s)'s
                     10: machine(s), they may otherwise contain severe bugs. Stable releases are
                     11: made available on a regular basis using the customary method: a message to
                     12: pari-announce.
                     13:
                     14: 1) First connection to the anonymous CVS server:
                     15: ================================================
                     16: Type the following commands from the shell
                     17:
                     18:   cvs -d :pserver:cvs@megrez.math.u-bordeaux.fr:/home/megrez/cvsroot login
                     19:
                     20: Hit return when asked for a password (there's no password); then back to
                     21: the shell prompt
                     22:
                     23:   cvs -z3 -d :pserver:cvs@megrez.math.u-bordeaux.fr:/home/megrez/cvsroot checkout pari
                     24:
                     25: This last command creates a local copy of the distribution from the
                     26: distant repository (in local directory 'pari'), using GNU gzip to compress
                     27: the files during the transfer [ if gzip is not installed on your machine,
                     28: remove the -z3 flag ].
                     29:
                     30: From now on, you can go to this pari directory and use any cvs command
                     31: directly (without the cryptic -d argument), as long as you remain there
                     32: (or in a subdirectory). Password won't be required again.
                     33:
                     34: 2) What can I do now ?
                     35: ======================
                     36:
                     37: * You can build pari in the usual way (see INSTALL) as if this 'pari'
                     38: directory had been created by fetching then extracting an archive on an FTP
                     39: server.
                     40:
                     41: * You can update your local copy at any time using 'cvs update', which will
                     42: put you in synch with the repository.
                     43:
                     44: * You can check exact differences between successive versions of a given file
                     45: by using 'cvs diff'. If you modify some files on your local copy, this also
                     46: enables you to track down your changes, and produce a patch. You won't be
                     47: able to commit your changes using anonymous access. Send the output of 'cvs
                     48: diff' [with flag -c if your local diff supports it] to the pari-dev mailing
                     49: list with a short description of what you've done, or to
                     50: pari@math.u-bordeaux.fr if you're not subscribed to pari-dev.
                     51:
                     52: If you plan to do that on a regular basis (which would be very nice :-),
                     53: send a note to pari-dev, telling what kind of development work you're
                     54: interested in, and ask for the rights to modify the repository directly.
                     55: Once this is granted, you'll be able to log in as 'cvsadmin' (the CVS
                     56: administrator) instead of 'cvs' (CVS user) as described above and you'll be
                     57: able to use 'cvs commit'.
                     58:
                     59:
                     60: NOTES and CAVEATS:
                     61: ==================
                     62: * you can speed up file transfers by using cvs -z3 (transfer files in
                     63: compressed format), e.g 'cvs -z3 update' if you've missed a lot of patches,
                     64: or 'cvs -z3 checkout' for the initial checkout. This requires that GNU gzip
                     65: be in your path. You can create a .cvsrc file in your home directory
                     66: containing lines of the form:
                     67:
                     68:     cvs -z3          [ use gzip -3 for all transfers ]
                     69:     diff -c          [ use diff -c (context diff) by default in 'cvs diff' ]
                     70:
                     71: * once you've run Configure, some files/directory will be created in the
                     72: local copy which are not under CVS control (only the master files are).
                     73: These are
                     74:
                     75:   O<OS>-<arch>*
                     76:   Makefile.O<OS>-<arch>*
                     77:   examples/Makefile.<OS>-<arch>
                     78:   doc/Makefile
                     79:   doc/gphelp
                     80:   doc/paricfg.tex
                     81:   doc/*.[aux | dvi | idx | log | ps | std | toc]
                     82:   emacs/pari.el
                     83:
                     84: After a global 'cvs diff', or 'cvs status', you can safely ignore all
                     85: messages pertaining to them (e.g "? doc/Makefile").
                     86:
                     87: * 'cvs diff' gives you the difference between your local copy and the
                     88: sources they were based on, not with the current state of the repository.
                     89: Use 'cvs diff -D now' for that.
                     90:
                     91: * All project files have an individual version number, independant of the
                     92: release numbering scheme. Official releases (starting from version 2.0.17)
                     93: are 'tagged' so that all files pertaining to a given release can be
                     94: simultaneously accessed without tracking version numbers. Tag names are
                     95: 'release-VERSION', e.g 'release-2-0-20'.
                     96:
                     97: * On Windows 95/98/2000 + Cygwin, you may have to explicitly set HOME (e.g
                     98: in your .bashrc) to some existing directory otherwise CVS will abort on
                     99: startup (when trying to create a .cvspass file).