Proposed update to cvsaccess.content
Vin Shelton
acs at xemacs.org
Wed Nov 25 23:05:12 EST 2009
This is still a work in progress (I haven't updated the R/W access
section), but I'm planning some fairly drastic surgery on
http://www.xemacs.org/Develop/cvsaccess.html. Comments, thoughts and
suggestions sought.
Many future updates are planned/required; at least hgaccess.content,
jobs.content and packages.content.
BTW, where do the page footers get generated? Those, too, could use
some updating.
- Vin
Index: Develop/ChangeLog
===================================================================
RCS file: /cvsroot/xemacs/XEmacs/xemacsweb/Develop/ChangeLog,v
retrieving revision 1.113
diff -a -u -r1.113 ChangeLog
--- Develop/ChangeLog 17 Apr 2009 13:19:32 -0000 1.113
+++ Develop/ChangeLog 26 Nov 2009 03:56:11 -0000
@@ -1,3 +1,11 @@
+2009-11-25 Vin Shelton <acs at xemacs.org>
+
+ * cvsaccess.content: Removed all reference to XEmacs 21.4, which
+ is now maintained in Mercurial. Generally cleaned up fairly
+ drastically. Commented out reference to 21.1 tree which is not
+ currently available at alioth. Commented out all references to
+ viewCVS, which is not currently available at alioth.
+
2009-04-17 Stephen J. Turnbull <stephen at xemacs.org>
* hgaccess.content: Fix some stupid typos.
Index: Develop/cvsaccess.content
===================================================================
RCS file: /cvsroot/xemacs/XEmacs/xemacsweb/Develop/cvsaccess.content,v
retrieving revision 1.32
diff -a -u -r1.32 cvsaccess.content
--- Develop/cvsaccess.content 4 Feb 2009 23:41:56 -0000 1.32
+++ Develop/cvsaccess.content 26 Nov 2009 03:56:11 -0000
@@ -5,27 +5,29 @@
Steve Youngs <youngs at xemacs.org>
Adrian Aichner <adrian at xemacs.org>
Stephen J. Turnbull <stephen at xemacs.org>
+Vin Shelton <acs at xemacs.org>
%main%
<h1>XEmacs CVS Repository</h1>
- <p>As of 5 December 2007, the development mainline (aka version
- 21.5) has been moved to a
+ <p>
+ The development mainline of XEmacs (currently version 21.5) and
+ the stable version of XEmacs (version 21.4) reside in
<a href="http://hgbook.red-bean.com/hgbook.html">Mercurial</a>
- repository on <code>hg.debian.org</code> from which you may
+ repositories on <code>hg.debian.org</code> from which you may
<a href="http://hg.debian.org/hg/xemacs/xemacs">browse</a> the
latest checked-in code. Please see the introduction to the
<a href="hgaccess.html">XEmacs Mercurial Repository</a> for
instructions on its use.</p>
- <p>Other XEmacs repositories, including the 21.4 branch, the
- packages, and the sources for this website, continue to be
- provided by the CVS repository on <code>cvs.xemacs.org</code>,
- hosted by our friends at <code>dotsrc.org</code>. This page
- describes access to those resources.</p>
-
- <p>Please review the information below even if you are familiar with
- the XEmacs CVS repository.</p>
+ <p>
+ <code>cvs.alioth.debian.org</code> hosts two different
+ <a href="http://www.cvshome.org/">CVS</a> (Concurrent Versions
+ System) trees for XEmacs. The primary CVS archive contains the
+ XEmacs package sources. These sources provide a large number of
+ customizable externally-provided packages for XEmacs. The other
+ CVS archive contains the source for this website and all of its
+ mirrors.
<ul>
@@ -35,73 +37,42 @@
<li><a href="#tutorial">Using the XEmacs CVS server</a></li>
- <li><a href="#tags">Tags: what they are and their use</a></li>
-
<li><a href="#packages">Packages info</a></li>
-
+<!--
<li><a href="#webaccess">Web access to the trees</a></li>
-
+-->
<li><a href="#committers">Commit (R/W) access to the CVS trees</a></li>
<li><a href="#recent">Recent news</a></li>
</ul>
- <p>
- This site has a collection of <a
- href="http://www.cvshome.org/">CVS</a> (Concurrent Versions
- System) trees for XEmacs, a feature-packed text-editing
- environment based on Lisp. XEmacs' best features are its
- extensibility, self-documentation, and its support for
- multilingual text processing, and is actively being developed by
- volunteers from all over the world. This site is intended for use
- by people wanting to hack on or test the sources. For more
- information, or for source/binary tarballs, check out the <a
- href="http://www.xemacs.org">XEmacs main WWW server</a>.</p>
-
- <p>
- The latest (21.5) development sources are no longer available
- under CVS. Please see the introduction to the <a
- href="hgaccess.html">XEmacs Mercurial Repository</a> for
- instructions on getting the 21.5 sources.
-
<h3><a name="quickstart">Quick Start Guide</a></h3>
<p>
First, you need to do, just once:</p>
<pre xml:space="preserve">
-$ <strong>cvs -d :pserver:cvs at cvs.xemacs.org:/pack/xemacscvs login</strong>
-(Logging in to cvs at sunsite.dk)
-CVS password: <strong>cvs</strong>
- </pre>
- To get the stable (21.4) development sources, do:
- <pre xml:space="preserve">
- <strong>cvs -z3 -d :pserver:cvs at cvs.xemacs.org:/pack/xemacscvs \
- checkout -d xemacs-21.4 -r release-21-4 xemacs</strong>
+$ <strong>cvs -d
:pserver:anonymous at cvs.alioth.debian.org:/cvsroot/xemacs
login</strong>
+There is no password, so press Enter when prompted for a password.
</pre>
+<!--
To get historical (21.1) development sources, do:
<pre xml:space="preserve">
<strong>cvs -z3 -d :pserver:cvs at cvs.xemacs.org:/pack/xemacscvs \
checkout -d xemacs-21.1 -r release-21-1 xemacs</strong>
</pre>
- The XEmacs lisp packages are now unbundled, and are available in
- their own CVS module. There is only one version of the XEmacs
- packages - no stable or unstable branch. Get them like this:
+-->
+ Retrieve the XEmacs packages like this:
<pre xml:space="preserve">
- <strong>cvs -z3 -d :pserver:cvs at cvs.xemacs.org:/pack/xemacscvs \
+ <strong>cvs -z3 -d
:pserver:anonymous at cvs.alioth.debian.org:/cvsroot/xemacs \
checkout packages</strong>
</pre>
-
- <p>
- Each of these components is available separately as non-CVS
- tarballs via ftp. Here are the current URL's:</p>
- <ul>
- <li><a href="http://ftp.xemacs.org/pub/xemacs/xemacs-21.5"><strong>http://ftp.xemacs.org/pub/xemacs/xemacs-21.5</strong></a></li>
- <li><a href="http://ftp.xemacs.org/pub/xemacs/xemacs-21.4"><strong>http://ftp.xemacs.org/pub/xemacs/xemacs-21.4</strong></a></li>
- <li><a href="http://ftp.xemacs.org/pub/xemacs/xemacs-21.1"><strong>http://ftp.xemacs.org/pub/xemacs/xemacs-21.1</strong></a></li>
- <li><a href="http://ftp.xemacs.org/pub/xemacs/packages"><strong>http://ftp.xemacs.org/pub/xemacs/packages</strong></a></li>
- </ul>
+ Retrieve a copy of the XEmacs website sources like this:
+ <pre xml:space="preserve">
+ <strong>cvs -z3 -d
:pserver:anonymous at cvs.alioth.debian.org:/cvsroot/xemacs \
+ checkout xemacsweb</strong>
+ </pre>
<hr />
<h3><a name="whatcvs">What is CVS?</a></h3>
@@ -126,13 +97,10 @@
versions.</p>
<p>
- Be warned that these trees are large! XEmacs 21 sources will take
- up almost 40 MB of hard drive space, before compilation. Add in
- the lisp packages tree (another 80 MB!) in your calculations if
- you're interested in messing with them too. All in all, the total
- tree size for the XEmacs core tree is 196MB, comprising over 2006
- files with 397754-some odd lines of code. Packages add another
- 4042 files for 760315 lines of lisp.</p>
+ Be warned that these trees are large! The lisp packages tree
+ takes up > 120MB of disk space. (The core sources retrieved
+ from the Mercurial archive also take up approximately 120MB.)
+ </p>
<hr />
<h3><a name="tutorial">Using the XEmacs CVS server</a></h3>
@@ -140,43 +108,29 @@
<p>
If you're interested in using the XEmacs CVS trees directly using
remote CVS, you'll need a version of CVS >= 1.9, with best results
- (currently) probably coming from 1.11. This server uses the
+ (currently) probably coming from 1.12. This server uses the
<strong>:pserver:</strong> protocol, with read-only access available for
- user <strong>cvs</strong>, password <strong>cvs</strong> (gee,
where did that come
- from?). The process goes something like this:</p>
+ user <strong>anonymous</strong>, with a blank password. The
+ process goes something like this:</p>
<p>
- First you need to log into <tt>SunSITE.dk</tt>. (<em>N.B.</em> We will
- alias this to <tt>cvs.xemacs.org</tt> again in the near future. You will
- then need to login again to check out modules with that hostname.
- However, old workspaces will continue to work automatically, with
- the explicit <tt>sunsite.dk</tt> hostname.) You only
+ First you need to log into the CVS server. You only
need to do this once, as it will create a file in your home
directory called <strong>.cvspass</strong> with the necessary data.</p>
<pre xml:space="preserve">
-pentagana [532]$ <strong>cvs -d
:pserver:cvs at cvs.xemacs.org:/pack/xemacscvs login</strong>
-(Logging in to cvs at sunsite.dk)
-CVS password: <i>(not echoed)</i><strong>cvs</strong>
+$ <strong>cvs -d
:pserver:anonymous at cvs.alioth.debian.org:/cvsroot/xemacs
login</strong>
+There is no password, so press Enter when prompted for a password.
</pre>
<p>
- Now go the the place you want to put the tree, and actually check
- out the current version.</p>
+ Now go the the place you want to put the XEmacs package tree, and check
+ out the packages.</p>
<pre xml:space="preserve">
-pentagana [533]$ <strong>cvs -z3 -d
:pserver:cvs at cvs.xemacs.org:/pack/xemacscvs \
- checkout -d xemacs-21.4 -r release-21-4 xemacs</strong>
- <i>(churn, churn, churn)</i>
+ <strong>cvs -z3 -d
:pserver:anonymous at cvs.alioth.debian.org:/cvsroot/xemacs \
+ checkout packages</strong>
</pre>
- <p>
- And voila! One <strong>xemacs-21.4</strong> directory complete with the
- latest versions of the base code. Packages are separate, of
- course.</p>
-
- <p>
- The <strong>-d</strong> option says what to name the new CVS directory
- tree.</p>
<p>
The <strong>-z3</strong> option enables compression during transit, and
@@ -190,13 +144,6 @@
impact on the CVS server machine is significant.</font></p>
<p>
- The <strong>-r</strong> option specifies the CVS branch to use.
- XEmacs 21.1 uses the branch <strong>release-21-1</strong>,
- which is in the same CVS module. The branch is not named
- something like <strong>xemacs-21.1</strong>, because periods are not
- permitted in a valid CVS branch name.</p>
-
- <p>
As it is ignored if not used on a network connection, you might
want to add it to your <strong>~/.cvsrc</strong> file for future use. You
could use a line like this:</p>
@@ -205,13 +152,13 @@
cvs -z3
</pre>
- Another neat something to put in there could be
+ Another useful option to put in <code>.cvsrc</code> is
<pre xml:space="preserve">
diff -u
</pre>
- which will make sure everything always comes out in unified diffs, and
+ which will make sure all diffs are generated as unified diffs, and
<pre xml:space="preserve">
checkout -P
@@ -231,7 +178,7 @@
checkout</strong></tt>).</p>
<pre xml:space="preserve">
-pentagana [533]$ <strong>cvs update</strong>
+<strong>cvs update</strong>
</pre>
<p>
@@ -239,48 +186,14 @@
update!) to properly track any changes to the directory structure
if you do not have that in your <strong>~/.cvsrc</strong> file.</p>
- <h3><a name="tags">A word about CVS tags</a></h3>
-
- <p>
- XEmacs developers do CVS commits on an irregular basis. The
- purpose behind this is to keep those actively coding on the same
- page. There is no guarantee that the current CVS sources even
- compile for anyone. This means that if you blindly do a <strong>cvs
- update</strong>, there is a chance that what you get is not
- functional.</p>
-
- <p>
- The way to get around this is to use the tag feature of CVS. All
- of the official releases (i.e. those available in tarball form on
- the ftp site) are at least minimally tested by the `release
- engineer' for that release. By specifying a tag to most CVS
- commands, you can tell it which version to grab (however, they
- default to the most recent in the branch you're working on). All
- of the 21.x releases are tagged in the format rMAJOR-MINOR-RELEASE
- (examples: XEmacs 21.4.22 is tagged r21-4-22). (Yes, this
- naming convention has changed from before. Old tags had names
- like r21-2b26.)</p>
-
- <p>
- The way you use this is by appending the <strong>-r <TAG></strong>
- option to the CVS command you want to use. Therefore, to update to
- 21.4.21 (but no further) from an earlier release, you'd
- type:</p>
-
- <pre xml:space="preserve">
-pentagana [533]$ <strong>cvs update -r r21-4-21</strong>
- </pre>
-
- <p>
- For more info, check your friendly CVS texinfo files.</p>
<hr />
- <h3><a name="packages">New Package system</a></h3>
+ <h3><a name="packages">Package Info</a></h3>
<p>
- For those of you wishing to work with XEmacs 21, you should
- probably know about our new packaging system. All the details are
+ For those of you wishing to work with XEmacs, you should
+ probably know about the packaging system. All the details are
available <a href="packages.html">here</a>, but for those of you
impatient to jump right in, here's the deal with the CVS trees
related to packages.</p>
@@ -291,7 +204,7 @@
<strong><PACKAGE-NAME></strong> for the module name. For example:</p>
<pre xml:space="preserve">
-pentagana [535]$ <strong>cvs -z3 -d
:pserver:cvs at cvs.xemacs.org:/pack/xemacscvs \
+ <strong>cvs -z3 -d
:pserver:anonymous at cvs.alioth.debian.org:/cvsroot/xemacs \
checkout gnus</strong>
</pre>
will get you a brand spanking new copy of gnus.
@@ -301,7 +214,7 @@
at once, and even set them up for easy compilation and
installation. To use that, simple grab the module
<strong>packages</strong>.</p>
-
+<!--
<hr />
<h3><a name="webaccess">Web Access using ViewCVS</a></h3>
@@ -351,7 +264,7 @@
<li><a href="http://cvs.xemacs.org/viewcvs.cgi/XEmacs/xemacsweb/">XEmacs
Website CVS tree</a></li>
</ul>
-
+-->
<hr />
<h3><a name="committers">Commit (R/W) access to the CVS trees</a></h3>
@@ -385,7 +298,7 @@
<li>
<p>
A history of submitting successful patches to
- <a href="http://list-archive.xemacs.org/xemacs-patches/">xemacs-patches</a></p></li>
+ <a href="http://calypso.tux.org/pipermail/xemacs-patches/">xemacs-patches</a></p></li>
<li>
<p>
@@ -564,106 +477,14 @@
<hr />
<h3><a name="recent"></a>News and changes</h3>
- <h5>2002-07-06</h5>
-
- <p>
- Changes by Steve Y:</p>
-
- <p>
- Update SSH instructions to include SSH version 2.</p>
-
- <h5>2001-12-09</h5>
+ <h5>2009-11-25</h5>
<p>
- All of the XEmacs CVS Repository (including its website) is now
- hosted by SunSITE.dk. The repository is browsable with ViewCVS,
- which offers these great features:</p>
+ Changes by Vin:</p>
- <ul>
- <li>Colorization for many file types via enscript.</li>
- <li>Bonsai-like <a
href="http://cvs.sunsite.dk/query.cgi?repository=%2Fpack%2Fxemacscvs&branch=&directory=&file=&who=&sortby=date&date=hours&hours=2">query</a>
features. (Requires MySQL and some other prerequisites)</li>
- <li>Annotation/blame viewing support against a read-only repository.</li>
- </ul>
-
- <h5>2001-11-08</h5>
-
- <p>
- Changes by Stephen:</p>
-
- <p>
- Fix bogus instructions from old CVS repository host, name of cvs
- administrator, etc.</p>
-
- <h5>2001-06-01</h5>
-
- <p>
- Changes by Steve Y:</p>
-
- <p>
- Modified references to the package tree to refer to the new
- <strong>packages</strong> CVS module.</p>
-
- <h5>2001-05-21</h5>
-
- <p>
- Changes by Stephen:</p>
-
- <p>
- <em>The Great Trunk Move</em> is documented.</p>
-
- <p>
- The ``top-level changes get lost in recursive commits'' bug is
- described.</p>
-
- <p>
- The version of CVS in use, and recommended, is now 1.11.</p>
-
- <p>
- XEmacs versions are updated: beta -> 21.5, gamma (new) -> 21.4,
- and stable remains 21.1.</p>
-
- <p>
- References to the xemacs-20 module are eliminated.</p>
-
- <h5>2000-01-04</h5>
-
- <p>
- Changes by Martin (?):</p>
-
- <p>
- A section on committing to the CVS tree has been added.</p>
-
- <p>
- The tag <strong>r21-2-latest-beta</strong> has been introduced.</p>
-
- <p>
- Many more people have CVS write access.</p>
-
- <p>
- We are planning the following changes in the future:</p>
-
- <ul>
- <li>Moving the unstable development branch to the CVS trunk, and
moving xemacs-21.1 onto a branch, probably release-21-1.</li>
- <li>Moving the web pages (like this page) under CVS control itself.</li>
- <li>Upgrade the CVS server to a nicer machine.</li>
- <li>Upgrade the version of the CVS server software to 1.10.x.</li>
- <li>Eliminate the currently required password on anonymous access.</li>
- </ul>
-
- <p>
- We've done a little reworking of the CVS tree, and to reduce
- confusion, the current tree has been renamed from
<strong>xemacs-20</strong>
- to just <strong>xemacs</strong>. For now symlinks are in place to keep
- things backwards compatible, but I don't know how long they're
- going to be there. Also, we've opened up the numbers of people who
- have write access to the tree, and so updates are going to me much
- more frequent. This means you probably will want to start working
- with tags in order to make sure you get a release or snapshot,
- instead of the current (potentially unstable) working copy (unless
- you REALLY want that...). For the moment, the head of the tree
- will still be the latest stable release (currently pre21.0) but
- this may change to where the head is our development area, and you
- will have to use tags to grab a particular version.</p>
+ <p>Since only the packages and the website are now maintained in CVS, I
+ removed much of the material from this page (including the 7
+ year-old <em>News</em> items).
<!-- Keep this comment at the end of the file
Local variables:
More information about the XEmacs-Patches
mailing list