"Fossies" - the Fresh Open Source Software Archive
Member "cvs-1.11.23/windows-NT/SCC/README.txt" (1 Sep 2005, 5006 Bytes) of package /linux/misc/old/cvs-1.11.23.tar.gz:
As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard
) with prefixed line numbers.
Alternatively you can here view
the uninterpreted source code file.
1 This is an experimental attempt to interface to the SCC API.
3 Note that this code doesn't (yet) do anything useful; this file
4 is currently for people who want to hack on the SCC interface,
5 not people who want a plug-in integration between any particular pair
6 of packages.
8 To install the test DLL, build scc.dll and then add the following
9 to the registry using the registry editor:
11 key/value what to put there
16 SCCServerName Concurrent Versions System
17 SCCServerPath <full pathname of scc.dll>
19 ProviderRegKey "SOFTWARE\CVS\CVS"
21 Concurrent Versions System "SOFTWARE\CVS\CVS"
23 Note that ProviderRegKey is the default source control
24 system, and InstalledSCCProviders list _all_ installed
25 source control systems. A development environment is allowed
26 to use either or both, so you should set both of them.
28 Note also that we are using "CVS" as the supplier of CVS.
29 CVS is not owned by any one company, so CVS seems like the
30 most appropriate string to put there.
32 If you do this right, then "Source Control" should appear
33 under the "Tools" menu (for Visual C++ 4.x; the details of course may
34 vary for other development environments).
36 NOW WHAT?
38 Well, I haven't yet figured out _all_ the different ways
39 that projects work at the SCC level. But here is what I
40 have done which has worked. SPECIAL NOTE: many paths are
41 hardcoded in scc.c, so you will need to fix that or put
42 things the same place I did. As you try the following you
43 will want to follow along in d:\debug.scc.
45 * Create a dummy project in d:\sccwork.
46 * On the Tools/Source Control menu, select "Share from CVS..."
47 * This will cause SccAddFromScc to be called, which will
48 claim there are two files, foo.c and bar.c, which should
49 appear as source controlled (grey) files in the file
51 * Now select one of the files and pick "Get Latest Version..."
52 from Tools/Source Control. You'll get a cheezy dialog (we
53 need to see why it is cheezy--by that I mean the size and
54 placement are funny), and if you say OK, then SccGet will
55 get called (which doesn't currently do anything).
57 TOOLS IMPLEMENTING THE SCC
59 I'm not sure whether we'll want to try to make this a comprehensive
60 list, but at least for the moment it seems worthwhile to list a few of
61 the programs which implement the Integrated Development Environment
62 (IDE) side of the SCC. Some of this information is based on rumor or,
63 worse yet, usenet posting, so it probably should be verified before
64 relying on it.
66 * Microsoft Developer Studio 4.x Professional (not Standard, not 2.x).
67 * Microsoft Access V7.0
68 * Powersoft's Optima++, PowerJ, and Power++
69 (not sure which versions, but this information was added in 1997 if
70 that helps. Someone on usenet reports 32 bit Powerbuilder version
71 5.03 but not version 4, version 5.0, or 16 bit Powerbuilder.).
72 * Premia's CodeWright editor
73 (versions 5.00b and 5.00c; not sure about older versions).
74 * HAHTsite (not sure what versions).
76 SPECIFICATIONS OR OTHER DOCUMENTS DESCRIBING THE SCC
78 The only publicly available document which we are aware of is pubscc.h
79 in this directory. This should be sufficient to get a start at
80 playing around with the SCC, and if you have done that and then
81 proceed to run into those areas which pubscc.h does not document well,
82 you are encouraged to send mail to firstname.lastname@example.org with your
85 OTHER INTERFACES
87 There are other interfaces which interface between a development
88 environment (or other front-end) and a source control system. That
89 is, in general terms they provide somewhat the function of the SCC,
90 although they may be at a somewhat different level and systems may
91 support/use several interfaces rather than it being an either/or thing.
93 If you know of other interfaces which should be added here I guess the
94 best place to make suggestions is email@example.com (although
95 the following list is not intended to be particularly CVS-centric).
97 * The CVS remote protocol is documented in doc/cvsclient.texi in the
98 CVS distribution and has at least 2 implementations of the client
99 (jCVS and CVS command line client), in addition to having been
100 implemented at least once by a special-purpose perl script.
102 * Microsoft's OLE Automation interface. The spec is available for
103 download at http://www.microsoft.com/ssafe. I'm not sure whether this
104 has been implemented by other source control systems. Metrowerks
105 implements this via a module which speaks the Metrowerks API out one
106 end and the OLE Automation interface out the other (the module runs on
107 Windows, not Mac).
109 * Symantec's Visual Cafe interface.
111 * Metrowerks publishes and implements the CodeWarrior IDE Version
112 Control System API. I think maybe the way to get a copy of the spec
113 is as part of CodeWarrior but I'm not completely clear on that.
115 For (some) more details on these interfaces, and others, see