Annotation of OpenXM_contrib/pari/CVS.DOC, Revision 1.1
1.1 ! maekawa 1: This file documents access to the CVS server, which is intended for PARI
! 2: developers or [alpha|beta]-testers who want the very latest bleeding edge
! 3: release. The CVS sources are guaranteed to compile cleanly and to pass the
! 4: bench suite on (one of) the administrator(s)'s machine(s), that's all. They
! 5: may otherwise contain severe bugs. Stable releases will be made available
! 6: on a regular basis using the customary method (a message to pari-announce).
! 7:
! 8:
! 9: First connection to the anonymous CVS server:
! 10:
! 11: cvs -d :pserver:cvs@megrez.math.u-bordeaux.fr:/home/megrez/cvsroot login
! 12: Hit return when asked for a password
! 13:
! 14: cvs -d :pserver:cvs@megrez.math.u-bordeaux.fr:/home/megrez/cvsroot checkout pari
! 15:
! 16: This last command will create a local copy of the distribution from the
! 17: repository (directory 'pari'). From now on, you can 'cd' to this pari
! 18: directory and use any cvs command without the -d argument, as long as you
! 19: remain there (or in a subdirectory). Password won't be required again. You
! 20: can also build pari in the usual way (see INSTALL). You can update your
! 21: local copy at any time using 'cvs update', which will put you in synch with
! 22: the repository.
! 23:
! 24: If you modify your local copy, you won't be able to commit your changes
! 25: using anonymous access. Use
! 26:
! 27: 'cvs diff' [with flag -c if your local diff supports it]
! 28:
! 29: Then send the output to the pari-dev mailing list with a short description
! 30: of what you've done [or to pari@math.u-bordeaux.fr if you're not subscribed
! 31: to pari-dev].
! 32:
! 33: If you plan to do that on a regular basis (which would be nice :-), send a
! 34: note to pari-dev, telling what kind of development work you're interested in,
! 35: and ask for the rights to modify the repository directly. Once this is
! 36: granted, you'll be able to log in as 'cvsadmin' (the CVS administrator)
! 37: instead of 'cvs' (CVS user) as described above and you'll be able to use 'cvs
! 38: commit' directly.
! 39:
! 40:
! 41: NOTES:
! 42: 1) you can speed up file transfers by using cvs -z9 (transfer files in
! 43: compressed format), e.g 'cvs -z9 update' if you've missed a lot of patches,
! 44: or 'cvs -z9 checkout' for the initial checkout. This requires that GNU gzip
! 45: be in your path.
! 46:
! 47: 2) once you've run Configure, some files/directory will be created in the
! 48: local copy which are not under CVS control (only the master files are).
! 49: These are
! 50:
! 51: O<OS>-<arch>/
! 52: O<OS>-<arch>.dbg/
! 53: O<OS>-<arch>.prf/
! 54: Makefile.O<OS>-<arch>
! 55: Makefile.O<OS>-<arch>.dbg
! 56: Makefile.O<OS>-<arch>.prf
! 57: examples/Makefile.<OS>-<arch>
! 58: doc/Makefile
! 59: doc/gphelp
! 60: doc/paricfg.tex
! 61: doc/*.[aux | dvi | idx | log | ps | std | toc]
! 62: emacs/pari.el
! 63:
! 64: After a global 'cvs diff', or 'cvs status', you can safely ignore all
! 65: messages pertaining to them (e.g "? doc/Makefile").
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>