25 |
1) Install CVS version 1.9 or later on your system. |
1) Install CVS version 1.9 or later on your system. |
26 |
|
|
27 |
2) Log into the CVS server: |
2) Log into the CVS server: |
28 |
|
|
29 |
$ cvs -d :pserver:anoncvs@subversions.gnu.org:/cvs login |
$ cvs -d :pserver:anoncvs@subversions.gnu.org:/cvs login |
30 |
|
|
31 |
At the prompt for `CVS password:', simply press the enter key. |
At the prompt for `CVS password:', simply press the enter key. |
81 |
|
|
82 |
Questions ============================================================ |
Questions ============================================================ |
83 |
|
|
|
(I don't know if they'll be "frequently asked" or not yet!) |
|
|
|
|
84 |
- It takes forever to do an update; what can I do to speed it up? |
- It takes forever to do an update; what can I do to speed it up? |
85 |
|
|
86 |
CVS tries to be smart about what it sends; it will transmit and |
CVS tries to be smart about what it sends; it will transmit and |
94 |
|
|
95 |
See the CVS documentation for more details. |
See the CVS documentation for more details. |
96 |
|
|
|
|
|
97 |
- What happens if I've changed files in my working directory, and then |
- What happens if I've changed files in my working directory, and then |
98 |
I do an update? |
I do an update? |
99 |
|
|
101 |
command will not overwrite them; instead, CVS will try to merge its |
command will not overwrite them; instead, CVS will try to merge its |
102 |
changes with your changes, as if you had applied a patch. Rejects are |
changes with your changes, as if you had applied a patch. Rejects are |
103 |
marked in the sources. |
marked in the sources. |
104 |
|
|
105 |
|
- How can I avoid horrible confusion when dealing with branches? |
106 |
|
|
107 |
|
Because the auto* tools are version control system agnostic, there is |
108 |
|
no support for regenerating files based on which branch of the source |
109 |
|
tree you are "on". This means that "cvs update -r BRANCH" will |
110 |
|
probably leave you w/ inconsistent configure, config.status, etc., |
111 |
|
which cannot be brought back into sync w/o re-running autogen.sh. |
112 |
|
|
113 |
|
So, the best advice is to: |
114 |
|
(1) dedicate a directory per branch; and |
115 |
|
(2) always run "./autogen.sh && ./configure ..." after a |
116 |
|
"cvs update -r BRANCH" |
117 |
|
|
118 |
|
If you do (1), you only need to do (2) once, so this is Recommended. |