Return to README CVS log

Up to [local] / OpenXM_contrib / pari

Annotation of OpenXM_contrib/pari/README, Revision 1.1.1.1

1.1       maekawa     1: This is PARI/GP, version 2.0.x.beta (*).
                      2:
                      3: The `beta' status means that a substantial amount of testing has been done,
                      4: but bugs might still be lurking in the code and the documentation might not
                      5: be absolutely accurate. Apart from this word of caution, we believe this
                      6: version is stable enough to be released for public use and for site-wide
                      7: installations.
                      8:
                      9: It is important for you and for us that you try this new version and send us
                     10: feedback, so than we can incorporate fixes and improvements into the
                     11: forthcoming `release' version. As usual for bug reports, try to make them
                     12: easily reproducible (using e.g. setrand(1)). Always include the GP header
                     13: and, if relevant, the Configure log.
                     14:
                     15: Some binaries can be found at the address
                     16:
                     17:   ftp://megrez.math.u-bordeaux.fr/pub/pari
                     18:
                     19: (*) Version numbers have the shape: MAJOR.MINOR.patchlevel.status. The status
                     20: increases through {alpha, beta, release}. New features are introduced during
                     21: the `alpha' phase, tested during `beta', and declared stable when `release'
                     22: is reached. The MAJOR version number (currently 2) won't change for a while,
                     23: the MINOR version number (0) increases when a new status cycle starts (as
                     24: soon as a `release' version is out), and the patchlevel goes up each time we
                     25: feel an upgrade is necessary (improvement, bugfix, ...). `Release' versions
                     26: may be updated with further patchlevels if sufficiently important bugs need
                     27: to be fixed before the next cycle reaches completion.
                     28: ==========================================================================
                     29:
                     30: To get started, run TeX on the file INSTALL.tex and have a look at the dvi
                     31: (extracted verbatim from Appendix A of the user manual). If you are in a
                     32: hurry, look at INSTALL.DOC (ascii file). But a lot of information is missing
                     33: there.
                     34:
                     35: Typing 'make doc' should typeset the PARI/GP user's manual, a tutorial and
                     36: reference card in directory doc.
                     37:
                     38: See the files NEW and COMPAT for new features and incompatible changes
                     39: respectively between 2.0 and older versions. See Changelog for (a terse
                     40: description of) subsequent patches.
                     41:
                     42: The file README.DOS is specific to DOS, OS/2 and Windows users.
                     43:
                     44: For the adventurous:
                     45: * If you want to check up-to-date, but possibly unstable, development
                     46: versions of PARI/GP or do development work yourself, see the file CVS.DOC.
                     47:
                     48: * Directory Odos/ contains information to compile binaries on DOS-based
                     49: systems (DOS, OS/2, Win3.1, Win95/98/NT/CE).
                     50:
                     51: Afterwards, you're on your own...
                     52:
                     53: ==========================================================================
                     54:
                     55: There are three mailing lists devoted to the PARI/GP package (run courtesy of
                     56: Dan Bernstein), and most feedback should be directed to those. They are:
                     57:
                     58: - pari-announce: to announce major version changes. You can't write to this
                     59: one, but you should probably subscribe.
                     60:
                     61: - pari-dev: for everything related to the development of PARI, including
                     62: suggestions, technical questions, bug reports or patch submissions.
                     63:
                     64: - pari-users: for everything else.
                     65:
                     66: To subscribe, send empty messages respectively to
                     67:
                     68:    pari-announce-subscribe@list.cr.yp.to
                     69:    pari-users-subscribe@list.cr.yp.to
                     70:    pari-dev-subscribe@list.cr.yp.to
                     71:
                     72: If you are not a member of any of those lists and don't want to become
                     73: one, you can write to us at
                     74:
                     75:   pari@math.u-bordeaux.fr
                     76:
                     77: At the very least, we will forward your mail to the lists above and correct
                     78: faulty behaviour, if necessary. But we cannot promise you will get an
                     79: individual answer.
                     80:
                     81: Last but not least, PARI home page (courtesy of Gerhard Niklasch) can be
                     82: found at
                     83:
                     84:   http://hasse.mathematik.tu-muenchen.de/ntsw/pari/
                     85:
                     86:   Thanks for your support, and have fun !