• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

extras/H03-May-2022-1,6551,214

test/H03-May-2022-4,8952,966

ArtisticH A D17-Jan-20026 KiB13299

CONFIGH A D03-May-20221.5 KiB6450

INSTALLH A D03-May-20225.3 KiB232166

MANIFESTH A D19-Apr-20028.5 KiB320262

NEWSH A D11-Oct-20058.5 KiB223158

READMEH A D11-Oct-20056.7 KiB193133

cvslinesH A D03-May-202235.3 KiB1,4641,017

cvslines-checkH A D19-Apr-200234.9 KiB1,2441,050

cvslines-commitH A D11-Oct-200517.6 KiB707565

cvslines-statusH A D07-Jun-20024.6 KiB193145

cvslines.1H A D03-May-202242.2 KiB1,1441,053

cvslines.configH A D17-Jan-20021.7 KiB5048

README

1
2cvslines Distribution Kit, Version 1.6.9
3
4Copyright 1996-1997, Network Appliance, Inc.
5Copyright 2002-2005, PiroNet NDH AG.
6
7This program is free software; you can redistribute it and/or modify
8it under the terms of the "Artistic License" which comes with this
9kit.
10
11See the file NEWS for a summary of what's new in the release.
12
13
14----- Introduction -------------------------------------------------------
15
16cvslines is a "wrapper" facility that helps out with merging changes
17between various cvs branches, where the branches represent different
18lines of development.
19
20cvslines takes the approach that it is often preferable to do such
21merges on a file-by file basis, at the time that changes are checked
22in to any line of development.
23
24cvslines offers the following advantages:
25
26 - Helps to solve the "you must remember to do it" problem;
27
28 - Tends to promote "doing it now" rather than delaying (or
29   procrastinating) the merging;
30
31 - Acts as a "wizard" to guide the user through the correct sequences
32   of cvs commands needed to merge changes from one line of
33   development into another.
34
35 - Can help to eliminate the creation of unnecessary RCS branches
36   among different lines of development, until they're really needed.
37
38cvslines should be viewed as a tool that helps you to use the
39capabilities inherent in CVS. There's nothing about using it that
40couldn't be done using "straight" cvs commands, and there's nothing to
41preclude any user from deciding to use it all the time, some of the
42time, or none of the time, as they prefer.
43
44For more information about using cvslines, see cvslines(1).
45
46Limitations:
47============
48 * cvslines doesn't work with binary files properly, this will be addressed
49   in a future release.
50 * There a are some special requirements for the Cygwin-Environment, this
51   might be addressed in a future release.
52
53----- Compatibility ------------------------------------------------------
54
55This release of cvslines requires perl 5, and has been tested with
56perl 5.6 and cvs >= 1.11.2. Older versions of cvs are no longer supported.
57
58Thus far, cvslines has been tested with following host operating
59systems:
60
61  Sun SunOS 4.x
62  Sun SunOS 5.x
63  DEC OSF1 V3.x
64  DEC OSF1 V4.x
65  Linux 2.0.x
66  Linux 2.2.x
67  Linux 2.4.x
68  Windows/Cygwin
69
70Please let us know if you find that it works (or not) in other
71environments, by posting to the cvslines forum at cvslines.sourceforge.net.
72
73Note concerning Cygwin:
74=======================
75
76You need to install the cygwin environment with Unix-Linefeed (the default),
77cvslines will fail to work if Cygwin is installed using DOS-Linefeeds. You
78also need to use the cygwin-cvs-client, a native Windows-client will not work.
79All source also need to be checked out using the cygwin client, otherwise
80the CVS-Control files will have DOS-Linefeeds which cvslines can't handle.
81
82----- Installation -------------------------------------------------------
83
84After you have unpacked the kit, you should have all the files listed
85in MANIFEST. MANIFEST is a perl script; when executed, it will tell
86you if anything is missing or has been altered.
87
88The script INSTALL will install the cvslines scripts, by copying them
89from the kit into the directories specified in a CONFIG file.
90
91MANIFEST and INSTALL expect to find perl 5 installed as
92/usr/local/bin/perl5; if there is no perl 5 interpreter found at that
93path in your environment, you'll have to specify the path to the perl5
94interpreter explicitly when you run them, e.g.,
95
96  % /some/other/place/perl INSTALL
97
98INSTALL is driven by a CONFIG file. At present there are only a few
99configuration parameters, which are explained by comments in the
100CONFIG file. The recommended approach for running INSTALL is to copy
101the CONFIG file supplied in the kit, edit the copy, and then invoke
102INSTALL with the edited file:
103
104  % cp CONFIG MYCONFIG
105  % vi CONFIG
106     {edit the configuration parameters as required}
107  % INSTALL MYCONFIG
108
109INSTALL will create five files and a symlink in $BINDIR
110(/usr/local/bin, in the template CONFIG):
111
112  /usr/local/bin/cvslines
113  /usr/local/bin/cvslines-config
114  /usr/local/bin/cvslines-check
115  /usr/local/bin/cvslines-commit
116  /usr/local/bin/cvslines-status
117  /usr/local/bin/cvslines_check -> cvslines
118
119It also installs the man page to $MAN1DIR (/usr/local/man/man1, in the
120template CONFIG).
121
122
123
124----- Testing ------------------------------------------------------------
125
126This kit contains some automated tests that you can use to help verify
127that cvslines is working correctly in your environment. They are in
128the "test" subdirectory within the kit, and are useful for helping to
129verify that cvslines will work properly with the perl interpreter and
130cvs binaries installed on your system.
131
132To run them, use:
133
134  % cd test; runCvslines
135
136This should run for a few minutes, producing lots of output. It all
137goes well, it will end with something like:
138
139case    : basic                    stat1.0_2                 PASS
140file    :   basic                  -    72 total cases:     72 passed;     0 failed;     0 notest
141summary :     runCvslines          -   406 total cases:       406 passed;     0 failed;     0 notest
142summary :     runCvslines          -     7 total files:         7 passed;     0 failed;     0 notest
143end     : runCvslines pass
144exit    : pass
145
146The test framework is written in perl.
147
148If it dies promptly upon trying to run the tests, then there may be
149some reason why the test framework won't run in your environment. The
150bulk of it is in the perl libraries in test/ttt.
151
152
153
154----- Configuration ------------------------------------------------------
155
156To complete the configuration of cvslines, you'll need to add
157appropriate entries in your $CVSROOT/CVSROOT/commitinfo for each cvs
158module you want to use cvslines with, and create a
159<repository>/cvslines.config file in the root directory of the
160repository tree for each CVS module in your repository (to define the
161lines of development that exist). You'll also need to create cvs
162branch tags for each line of development you have defined, if they
163don't already exist.
164
165See the cvslines(1) man page for further information on how to set up
166these files.
167
168
169
170----- Support ------------------------------------------------------------
171
172cvslines is primarily an internal tool used at Network Appliance and at
173PiroNet NDH AG.
174For support post your questions at the forums on cvslines.sourceforge.net.
175
176Include as much relevant information as you can, including the output
177from "cvslines version".
178
179If you can, include a cvslines log file (which, with the default
180CONFIG, will be written in /usr/adm/cvslines.log, or ~/cvslines.log).
181
182Authors:
183
184  Richard Geiger (Original Author)
185  rmg@netapp.com (might not work any more)
186
187  J�rgen Jatzkowski (Bugfixing and Enhancements)
188  jjatzkowski@pironet-ndh.com
189
190  Ingo Rockel (Bugfixing and Enhancements)
191  irockel@pironet-ndh.com
192
193