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.2

1.2     ! noro        1: The Concurrent Versions System (CVS, see http://www.cyclic.com) provides
1.1       noro        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
1.2     ! noro        9: may contain severe bugs, benches may fail, they may not even compile. Stable
        !            10: releases are made available on a regular basis using the customary method:
        !            11: a message to pari-announce.
1.1       noro       12:
                     13: 1) First connection to the anonymous CVS server:
                     14: ================================================
                     15: Type the following commands from the shell
                     16:
                     17:   cvs -d :pserver:cvs@megrez.math.u-bordeaux.fr:/home/megrez/cvsroot login
                     18:
                     19: Hit return when asked for a password (there's no password); then back to
                     20: the shell prompt
                     21:
                     22:   cvs -z3 -d :pserver:cvs@megrez.math.u-bordeaux.fr:/home/megrez/cvsroot checkout pari
                     23:
                     24: This last command creates a local copy of the distribution from the
                     25: distant repository (in local directory 'pari'), using GNU gzip to compress
                     26: the files during the transfer [ if gzip is not installed on your machine,
                     27: remove the -z3 flag ].
                     28:
                     29: From now on, you can go to this pari directory and use any cvs command
                     30: directly (without the cryptic -d argument), as long as you remain there
                     31: (or in a subdirectory). Password won't be required again.
                     32:
                     33: 2) What can I do now ?
                     34: ======================
                     35:
                     36: * You can build pari in the usual way (see INSTALL) as if this 'pari'
1.2     ! noro       37: directory had been created by fetching, then extracting, an archive on an FTP
1.1       noro       38: server.
                     39:
                     40: * You can update your local copy at any time using 'cvs update', which will
                     41: put you in synch with the repository.
                     42:
                     43: * You can check exact differences between successive versions of a given file
                     44: by using 'cvs diff'. If you modify some files on your local copy, this also
                     45: enables you to track down your changes, and produce a patch. You won't be
                     46: able to commit your changes using anonymous access. Send the output of 'cvs
1.2     ! noro       47: diff' [ with flag -c if your local diff supports it ] to the pari-dev mailing
1.1       noro       48: list with a short description of what you've done, or to
                     49: pari@math.u-bordeaux.fr if you're not subscribed to pari-dev.
                     50:
                     51: If you plan to do that on a regular basis (which would be very nice :-),
                     52: send a note to pari-dev, telling what kind of development work you're
                     53: interested in, and ask for the rights to modify the repository directly.
                     54: Once this is granted, you'll be able to log in as 'cvsadmin' (the CVS
                     55: administrator) instead of 'cvs' (CVS user) as described above and you'll be
                     56: able to use 'cvs commit'.
                     57:
1.2     ! noro       58: 3) Version tags:
        !            59: ================
1.1       noro       60:
1.2     ! noro       61: All project files have an individual version number, independent of the
        !            62: release numbering scheme. Official releases (starting from version 2.0.17)
        !            63: are 'tagged' so that all files pertaining to a given release can be
        !            64: simultaneously accessed without tracking version numbers. Tag names are
        !            65: 'release-<VERSION>' with dots replaced by dashes, e.g 'release-2-0-20' for
        !            66: 2.0.20.
        !            67:
        !            68: If you want to fetch a specific version of pari (2.0.17 or more recent), add
        !            69: the argument '-r <TAG>' to your checkout or update command. The tag
        !            70: 'release-2-1-patches' denotes the stable branch 2.1 as a whole, and can be
        !            71: used to checkout up to date sources from that branch in between releases. For
        !            72: instance:
        !            73:
        !            74:   cvs update -r release-2-1-patches
        !            75:
        !            76: produces the latest stable distribution with all relevant patches [the ones
        !            77: not affecting stability] backported.
        !            78:
        !            79: TIPS and CAVEATS:
        !            80: =================
1.1       noro       81: * you can speed up file transfers by using cvs -z3 (transfer files in
                     82: compressed format), e.g 'cvs -z3 update' if you've missed a lot of patches,
                     83: or 'cvs -z3 checkout' for the initial checkout. This requires that GNU gzip
1.2     ! noro       84: be in your path.
        !            85:
        !            86: * You can create a .cvsrc file in your home directory containing lines of the
        !            87: form:
1.1       noro       88:
                     89:     cvs -z3          [ use gzip -3 for all transfers ]
                     90:     diff -c          [ use diff -c (context diff) by default in 'cvs diff' ]
                     91:
                     92: * 'cvs diff' gives you the difference between your local copy and the
                     93: sources they were based on, not with the current state of the repository.
                     94: Use 'cvs diff -D now' for that.
                     95:
                     96: * On Windows 95/98/2000 + Cygwin, you may have to explicitly set HOME (e.g
                     97: in your .bashrc) to some existing directory otherwise CVS will abort on
                     98: startup (when trying to create a .cvspass file).