1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
|
<?php
// Vim Documentation
require_once("include/init.inc");
$page_title = "Vim from CVS";
include("header.php");
?>
<h1>The Vim CVS repository</h1>
<p>
Vim, like many open source projects, is distributed with the aid of the
<a href='http://www.cvshome.org'>Concurrent Versioning System</a>
(CVS). CVS allows developers to maintain a single, controlled source
tree with multiple check-outs of individual files.
</p>
<p>
If you don't know how to use CVS, you'll probably want to look at the
<a href='http://www.cvshome.org/docs/#s2'>official guides</a>. It's a
powerful, but complicated piece of software.
</p>
<h1>Browsing the Vim sources</h1>
<p>
You can browse the CVS <a href='http://vim.cvs.sourceforge.net/vim/'>online at SourceForge</a>. This shows the most recent version of the files, both the released version "vim" and the development version "vim7". You can view diffs to find out what the latest changes are.
</P>
<P>
Documentation on accessing it via pserver or ssh can be found on the
<a href='http://sourceforge.net/cvs/?group_id=8'>SourceForge project page</a>.
<p>
<h1>Obtaining Vim through CVS</h1>
<p>
SourceForge sometimes has problems with the CVS server.
You might want to use
<a href="/subversion.php">Subversion</a> instead.
</p>
<p>
These are the simple instructions how to obtain the Vim files through CVS.
Use this when you have a reasonable fast internet connection and want to
compile Vim yourself.
It should work well on any system that supports CVS.
</p>
<p id='update_freq'>
<strong>Note:</strong> The CVS repository is regularly, but not
immediately. Vim's CVS repository may be a few days behind the head of
development. For information on patching Vim with the most up-to-date
patches, consult the <a href='/download.php#patches'>information on
patches</a>
</p>
<h2>Doing it for the first time</h2>
Go to a directory where you want the Vim source tree to appear. Use this
command (it is one line):
<p>
<table cellpadding="0" cellspacing="0" border="0">
<tr>
<td> </td>
<td>
<code>cvs -z3 -d:pserver:anonymous@vim.cvs.sf.net:/cvsroot/vim checkout vim7</code>
</td>
</tr>
</table>
<p>
This will create the "vim7" directory and download all the Vim files and
subdirectories into it. It should also work when you are behind a firewall,
because it uses port 80. It probably doesn't work with a proxy though.
<br>
Read the "vim7/README.txt" file for how to compile Vim.
For Unix it's simply "cd vim7/src; make".
<P>
<h2>Updating</h2>
Recent patches appear in CVS all the time. Change into the "vim7" directory and
include the changes with this single command:
<p>
<table cellpadding="0" cellspacing="0" border="0">
<tr>
<td> </td>
<td>
<code>cvs -z3 update</code>
</td>
</tr>
</table>
<p>
You will get messages for all directories that are inspected and files that are
being updated.
<P>
<br>
<h1>Obtaining Vim through CVS with Aap</h1>
Aap is a new tool that does all the work of downloading for you. You
download one file, called a recipe, and "aap install" does all the work. To
later update to the latest version of Vim you do not need to download anything
manually or type the CVS root URL, just use the command "aap update".
<p>
The detailed explanation can be found
<a href="http://www.a-a-p.org/ports.html">here</a>.
Please report problems to Bram AT a-a-p.org.
<?php
$google_ads = "normal";
include("footer.php");
?>
|
