diff --git a/doc/src/sgml/cvs.sgml b/doc/src/sgml/cvs.sgml index 32f4c27c3e..254bc1e7ff 100644 --- a/doc/src/sgml/cvs.sgml +++ b/doc/src/sgml/cvs.sgml @@ -1,4 +1,4 @@ - + @@ -23,7 +23,7 @@ The PostgreSQL source code is stored and managed using the - CVS code management system. + CVS version control system. @@ -50,10 +50,9 @@ You will need a local copy of CVS (Concurrent Version Control System), which you can get from - - (the official site with the latest version) or any GNU software - archive site (often somewhat outdated). We recommend version 1.10 - or newer. Many systems have a recent version of + (the official + site with the latest version) or any GNU software archive site + (often somewhat outdated). Many systems have a recent version of cvs installed by default. @@ -72,7 +71,7 @@ cvs -d :pserver:anoncvs@anoncvs.postgresql.org:/projects/cvsroot login You should only need to do this once, since the password will be - saved in .cvspass in your home directory. + saved in .cvspass in your home directory. @@ -143,29 +142,13 @@ cvs update - - - Some older versions of CVS have a bug that - causes all checked-out files to be stored world-writable in your - directory. If you see that this has happened, you can do something like - -chmod -R go-w pgsql - - to set the permissions properly. - This bug is fixed as of - CVS version 1.9.28. - - - - CVS can do a lot of other things, - such as fetching prior revisions - of the PostgreSQL sources - rather than the latest development version. - For more info consult the manual that comes with - CVS, or see the online - documentation at - . + CVS can do a lot of other things, such + as fetching prior revisions of the + PostgreSQL sources rather than the + latest development version. For more info consult the manual that + comes with CVS, or see the online + documentation at . @@ -478,222 +461,5 @@ pgsql - - - Installing <productname>CVSup</productname> - - - CVSup is available as source, pre-built - binaries, or Linux RPMs. It is far easier to use a binary than to - build from source, primarily because the very capable, but - voluminous, Modula-3 compiler is required for the build. - - - - <productname>CVSup</productname> Installation from Binaries - - - You can use pre-built binaries - if you have a platform for which binaries - are posted on the PostgreSQL - - ftp site - or if you are running FreeBSD, for which - CVSup is available as a port. - - - - CVSup was originally developed as a - tool for distributing the FreeBSD - source tree. It is available as a port, and for those running - FreeBSD, if this is not sufficient to tell how to obtain and - install it then please contribute a procedure here. - - - - - - At the time of writing, binaries are available for - Alpha/Tru64, ix86/xBSD, - HPPA/HP-UX 10.20, MIPS/IRIX, - ix86/linux-libc5, ix86/linux-glibc, - Sparc/Solaris, and Sparc/SunOS. - - - - - Retrieve the binary tar file for - cvsup - (cvsupd is not required - to be a client) appropriate for your platform. - - - - - - If you are running FreeBSD, install the CVSup port. - - - - - - If you have another platform, check for and download the appropriate binary from - the PostgreSQL - - ftp site. - - - - - - - - Check the tar file to verify the contents and directory - structure, if any. For the linux tar file at least, the static binary - and man page is included without any directory packaging. - - - - - - If the binary is in the top level of the tar file, then simply - unpack the tar file into your target directory: - - -cd /usr/local/bin -tar zxvf /usr/local/src/cvsup-16.0-linux-i386.tar.gz -mv cvsup.1 ../doc/man/man1/ - - - - - - - If there is a directory structure in the tar file, then unpack - the tar file within /usr/local/src and move the binaries into - the appropriate location as above. - - - - - - - - Ensure that the new binaries are in your path. - - -$ rehash -$ which cvsup -$ set path=(path to cvsup $path) -$ which cvsup -/usr/local/bin/cvsup - - - - - - - - Installation from Sources - - - Installing CVSup from sources is not - entirely trivial, primarily because most systems will need to - install a Modula-3 compiler first. - This compiler is available as Linux RPM, - FreeBSD package, or source code. - - - - A clean-source installation of Modula-3 takes roughly 200MB of disk space, - which shrinks to roughly 50MB of space when the sources are removed. - - - - - Linux installation - - - - Install Modula-3. - - - - - - Pick up the Modula-3 - distribution from - Polytechnique Montréal - who are actively maintaining the code base originally developed by - the - DEC Systems Research Center. - The PM3 RPM distribution is roughly - 30MB compressed. At the time of writing, the 1.1.10-1 release - installed cleanly on RH-5.2, whereas the 1.1.11-1 release is - apparently built for another release (RH-6.0?) and does not run on RH-5.2. - - - - This particular rpm packaging has - many RPM files, - so you will likely want to place them into a separate - directory. - - - - - - - - Install the Modula-3 RPMs: - - -# rpm -Uvh pm3*.rpm - - - - - - - - - Unpack the cvsup distribution: - - -# cd /usr/local/src -# tar zxf cvsup-16.0.tar.gz - - - - - - - Build the cvsup distribution, suppressing the GUI interface - feature to avoid requiring X11 libraries: - - -# make M3FLAGS="-DNOGUI" - - - and if you want to build a static binary to move to systems - that may not have Modula-3 installed, try: - - -# make M3FLAGS="-DNOGUI -DSTATIC" - - - - - - - Install the built binary: - - -# make M3FLAGS="-DNOGUI -DSTATIC" install - - - - -