At least two methods,
- anonymous CVS and
CVSup,
- are available to pull the
CVS code tree from the
+ anonymous CVS and
CVSup,
+ are available to pull the
CVS code tree from the
PostgreSQL server to your local machine.
If you would like to keep up with the current sources on a regular
- basis, you can fetch them from our
CVS server
+ basis, you can fetch them from our
CVS server
retrieve updates from time to time.
- You will need a local copy of
CVS + You will need a local copy of
CVS (Concurrent Version Control System), which you can get from
http://www.cyclic.com/ or
- any GNU software archive site.
+ any GNU software archive site.
We currently recommend version 1.10 (the most recent at the time
- of writing). Many systems have a recent version of
+ of writing). Many systems have a recent version of
cvs installed by default.
- which installs the
PostgreSQL sources into a
+ which installs the
PostgreSQL sources into a
subdirectory pgsql
of the directory you are currently in.
$ chmod -R go-w pgsql
to set the permissions properly.
- This bug is fixed as of
+ This bug is fixed as of
When you tag more than one file with the same tag you can think
about the tag as a curve drawn through a matrix of filename vs.
revision number. Say we have 5 files with the following revisions:
-
+
file1 file2 file3 file4 file5
-
+
1.1 1.1 1.1 1.1 /--1.1* <-*- TAG
1.2*- 1.2 1.2 -1.2*-
1.3 \- 1.3*- 1.3 / 1.3
Getting The Source Via <productname>CVSup</productname>
- An alternative to using anonymous CVS for retrieving
+ An alternative to using anonymous CVS for retrieving
the
PostgreSQL source tree
- Decide where you want to keep your local copy of the
+ Decide where you want to keep your local copy of the
CVS repository. On one of our systems we
- recently set up a repository in /home/cvs/,
+ recently set up a repository in /home/cvs/,
but had formerly kept it under a
PostgreSQL development tree in
/opt/postgres/cvs/. If you intend to keep your
in your .cshrc file, or a similar line in
your .bashrc or
- .profile file, depending on your shell.
+ .profile file, depending on your shell.
which cvsup
- Then, simply run
+ Then, simply run
# prefix directory where CVSup will store the actual distribution(s)
*default prefix=/home/cvs
-# complete distribution, including all below
+# complete distribution, including all below
pgsql
# individual distributions vs 'the whole thing'
# prefix directory where CVSup will store the actual distribution(s)
*default prefix=/usr/local/pgsql
-# complete distribution, including all below
+# complete distribution, including all below
pgsql
# individual distributions vs 'the whole thing'
Installing <productname>CVSup</productname>
-
CVSup is available as source, pre-built
+
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.
You can use pre-built binaries
if you have a platform for which binaries
- are posted on
+ are posted on
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
+ 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.
If you are running FreeBSD, install the
CVSup port.
-
+
If you have another platform, check for and download the appropriate binary from
- If the binary is in the top level of the tar file, then simply
+ If the binary is in the top level of the tar file, then simply
unpack the tar file into your target directory:
- If there is a directory structure in the tar file, then unpack
+ 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.
distribution from
- who are actively maintaining the code base originally developed by
+ who are actively maintaining the code base originally developed by
url="http://www.research.digital.com/SRC/modula-3/html/home.html">the DEC Systems Research Center.
The
PM3 RPM distribution is roughly
John
I've deposited a statically built cvsup client executable (and man pages
-and test configuration) in
+and test configuration) in
/pub/incoming/cvsup-15.1-client-linux.tar.gz
the makefiles with two commands each. Not difficult at all. John gives
some hints in his e-mail on how to build a static executable, and on how
to shrink the size of the executable by leaving out the GUI support.
-Again, easy to do.
+Again, easy to do.
My client test case, picking up a sub-tree of the FreeBSD distribution,
worked flawlessly. I haven't tried running a server.
projects / postgresql.git / commitdiff