pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Vince Vielhaber <vev@michvhf.com>
Cc: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: [HACKERS] CVS changes
Date: Tue, 2 Oct 2001 15:34:09 -0400 (EDT)
Message-ID: <200110021934.f92JY9P27352@candle.pha.pa.us> (raw)
In-Reply-To: <Pine.BSF.4.30.0110021529230.384-100000@paprika.michvhf.com>

> On Tue, 2 Oct 2001, Bruce Momjian wrote:
> 
> > Vince, can you update:
> >
> > 	/usr/local/www/developer/TODO/docs/cvs.html
> >
> > to use the right CVS locations or give me permission to modify it.
> 
> Where is the new one hiding?

Uh, we are not building SGML yet.  Here is the HTML file that is current
from my machine.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Attachments:

/tmp/cvs.html (text/html, 7.3K) download <HTML ><HEAD ><TITLE >The CVS Repository</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.64 "><LINK REV="MADE" HREF="mailto:pgsql-docs@postgresql.org"><LINK REL="HOME" TITLE="PostgreSQL 7.2 Documentation" HREF="index.html"><LINK REL="UP" TITLE="PostgreSQL 7.2 Developer's Guide" HREF="developer.html"><LINK REL="PREVIOUS" TITLE="For the Programmer" HREF="nls-programmer.html"><LINK REL="NEXT" TITLE="CVS Tree Organization" HREF="cvs-tree.html"><LINK REL="STYLESHEET" TYPE="text/css" HREF="stylesheet.css"><META NAME="creation" CONTENT="2001-10-01T22:56:41"></HEAD ><BODY CLASS="APPENDIX" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#840084" ALINK="#0000FF" ><DIV CLASS="NAVHEADER" ><TABLE WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TH COLSPAN="3" ALIGN="center" >PostgreSQL 7.2 Documentation</TH ></TR ><TR ><TD WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A HREF="nls-programmer.html" >Prev</A ></TD ><TD WIDTH="80%" ALIGN="center" VALIGN="bottom" ></TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A HREF="cvs-tree.html" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="APPENDIX" ><H1 ><A NAME="CVS" >Appendix DG1. The <SPAN CLASS="PRODUCTNAME" >CVS</SPAN > Repository</A ></H1 ><DIV CLASS="TOC" ><DL ><DT ><B >Table of Contents</B ></DT ><DT >DG1.1. <A HREF="cvs.html#ANONCVS" >Getting The Source Via Anonymous <SPAN CLASS="PRODUCTNAME" >CVS</SPAN ></A ></DT ><DT >DG1.2. <A HREF="cvs-tree.html" ><SPAN CLASS="PRODUCTNAME" >CVS</SPAN > Tree Organization</A ></DT ><DT >DG1.3. <A HREF="cvsup.html" >Getting The Source Via <SPAN CLASS="PRODUCTNAME" >CVSup</SPAN ></A ></DT ></DL ></DIV ><P > The <SPAN CLASS="PRODUCTNAME" >Postgres</SPAN > source code is stored and managed using the <SPAN CLASS="PRODUCTNAME" >CVS</SPAN > code management system. </P ><P > At least two methods, anonymous CVS and <SPAN CLASS="PRODUCTNAME" >CVSup</SPAN >, are available to pull the <SPAN CLASS="PRODUCTNAME" >CVS</SPAN > code tree from the <SPAN CLASS="PRODUCTNAME" >Postgres</SPAN > server to your local machine. </P ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A NAME="ANONCVS" >DG1.1. Getting The Source Via Anonymous <SPAN CLASS="PRODUCTNAME" >CVS</SPAN ></A ></H1 ><P > If you would like to keep up with the current sources on a regular basis, you can fetch them from our <SPAN CLASS="PRODUCTNAME" >CVS</SPAN > server and then use <SPAN CLASS="PRODUCTNAME" >CVS</SPAN > to retrieve updates from time to time. </P ><DIV CLASS="PROCEDURE" ><P ><B >Anonymous CVS</B ></P ><OL TYPE="1" ><LI ><P > You will need a local copy of <SPAN CLASS="PRODUCTNAME" >CVS</SPAN > (Concurrent Version Control System), which you can get from <A HREF="http://www.cyclic.com/" TARGET="_top" >http://www.cyclic.com/</A > or 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 <SPAN CLASS="APPLICATION" >cvs</SPAN > installed by default. </P ></LI ><LI ><P > Do an initial login to the <SPAN CLASS="PRODUCTNAME" >CVS</SPAN > server: </P><PRE CLASS="PROGRAMLISTING" >$ cvs -d :pserver:anoncvs@anoncvs.postgresql.org:/projects/cvsroot login </PRE ><P> You will be prompted for a password; just press <TT CLASS="LITERAL" >ENTER</TT >. You should only need to do this once, since the password will be saved in <TT CLASS="LITERAL" >.cvspass</TT > in your home directory. </P ></LI ><LI ><P > Fetch the <SPAN CLASS="PRODUCTNAME" >Postgres</SPAN > sources: </P><PRE CLASS="PROGRAMLISTING" >cvs -z3 -d :pserver:anoncvs@anoncvs.postgresql.org:/projects/cvsroot co -P pgsql </PRE ><P> which installs the <SPAN CLASS="PRODUCTNAME" >Postgres</SPAN > sources into a subdirectory <TT CLASS="FILENAME" >pgsql</TT > of the directory you are currently in. </P><DIV CLASS="NOTE" ><BLOCKQUOTE CLASS="NOTE" ><P ><B >Note: </B > If you have a fast link to the Internet, you may not need <TT CLASS="OPTION" >-z3</TT >, which instructs <SPAN CLASS="PRODUCTNAME" >CVS</SPAN > to use gzip compression for transferred data. But on a modem-speed link, it's a very substantial win. </P ></BLOCKQUOTE ></DIV ><P> </P ><P > This initial checkout is a little slower than simply downloading a <TT CLASS="FILENAME" >tar.gz</TT > file; expect it to take 40 minutes or so if you have a 28.8K modem. The advantage of <SPAN CLASS="PRODUCTNAME" >CVS</SPAN > doesn't show up until you want to update the file set later on. </P ></LI ><LI ><P > Whenever you want to update to the latest <SPAN CLASS="PRODUCTNAME" >CVS</SPAN > sources, <B CLASS="COMMAND" >cd</B > into the <TT CLASS="FILENAME" >pgsql</TT > subdirectory, and issue </P><PRE CLASS="PROGRAMLISTING" >$ cvs -z3 update -d -P </PRE ><P> This will fetch only the changes since the last time you updated. You can update in just a couple of minutes, typically, even over a modem-speed line. </P ></LI ><LI ><P > You can save yourself some typing by making a file <TT CLASS="FILENAME" >.cvsrc</TT > in your home directory that contains </P><PRE CLASS="PROGRAMLISTING" >cvs -z3 update -d -P </PRE ><P> This supplies the <TT CLASS="OPTION" >-z3</TT > option to all cvs commands, and the <TT CLASS="OPTION" >-d</TT > and <TT CLASS="OPTION" >-P</TT > options to cvs update. Then you just have to say </P><PRE CLASS="PROGRAMLISTING" >$ cvs update </PRE ><P> to update your files. </P ></LI ></OL ></DIV ><DIV CLASS="CAUTION" ><P ></P ><TABLE CLASS="CAUTION" BORDER="1" WIDTH="100%" ><TR ><TD ALIGN="CENTER" ><B >Caution</B ></TD ></TR ><TR ><TD ALIGN="LEFT" ><P > Some older versions of <SPAN CLASS="PRODUCTNAME" >CVS</SPAN > 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 </P><PRE CLASS="PROGRAMLISTING" >$ chmod -R go-w pgsql </PRE ><P> to set the permissions properly. This bug is fixed as of <SPAN CLASS="PRODUCTNAME" >CVS</SPAN > version 1.9.28. </P ></TD ></TR ></TABLE ></DIV ><P > <SPAN CLASS="PRODUCTNAME" >CVS</SPAN > can do a lot of other things, such as fetching prior revisions of the <SPAN CLASS="PRODUCTNAME" >Postgres</SPAN > sources rather than the latest development version. For more info consult the manual that comes with <SPAN CLASS="PRODUCTNAME" >CVS</SPAN >, or see the online documentation at <A HREF="http://www.cyclic.com/" TARGET="_top" >http://www.cyclic.com/</A >. </P ></DIV ></DIV ><DIV CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><A HREF="nls-programmer.html" >Prev</A ></TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="index.html" >Home</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" ><A HREF="cvs-tree.html" >Next</A ></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >For the Programmer</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="developer.html" >Up</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" ><SPAN CLASS="PRODUCTNAME" >CVS</SPAN > Tree Organization</TD ></TR ></TABLE ></DIV ></BODY ></HTML >

view thread (70+ messages)  latest in thread

Message-ID: <200110021934.f92JY9P27352@candle.pha.pa.us>
Permalink:  ../200110021934.f92JY9P27352@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200110021934.f92JY9P27352@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: pgman@candle.pha.pa.us, vev@michvhf.com
  Subject: Re: [HACKERS] CVS changes
  In-Reply-To: <200110021934.f92JY9P27352@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox